linkedin / linkedin/LayoutTest-iOS
Getting Test Failure due to UITableViewWrapperView overlapping UIImageView
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 558
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
I am getting the following test failure while layout testing my View Controller:
failed - Bottom right corner of <UITableViewWrapperView: 0x7f8b9f1aca00; frame = (0 0; 375 559); gestureRecognizers = <NSArray: 0x608000251d90>; layer = <CALayer: 0x6080002311c0>; contentOffset: {0, 0}; contentSize: {375, 559}> overlaps upper left corner of <UIImageView: 0x7f8b9d75c260; frame = (3 553.5; 369 2.5); alpha = 0; opaque = NO; autoresize = TM; userInteractionEnabled = NO; layer = <CALayer: 0x608000230ee0>>. If this is intentional, you should add one of the views to viewsAllowingOverlap.
However, my ViewController does not have any UIImageView elements. Do I need to add table view to viewClassesAllowingSubviewErrors?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported layout-test failure and the ViewController context, then trace how UITableViewWrapperView, UIImageView, viewsAllowingOverlap, and viewClassesAllowingSubviewErrors are handled. Done means determining why an undeclared UIImageView is reported and whether the issue requires an allowlist change or another correction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- objective-c
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100