Juanpe/SkeletonView

IOS 16.1 crash

Open

#512 opened on Sep 19, 2022

View on GitHub
 (3 comments) (3 reactions) (0 assignees)Swift (1,125 forks)batch import
good first issuetriaged🐞 bug

Repository metrics

Stars
 (12,873 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Description

iOS 16.1 beta version crashed

What type of issue is this? (place an x in one of the [ ])

  • [ x] bug
  • enhancement (feature request)
  • question
  • documentation related
  • discussion

Requirements (place an x in each of the [ ])

  • [x ] I've read and understood the Contributing guidelines and have done my best effort to follow them.
  • [x ] I've read and agree to the Code of Conduct.
  • [ x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report

iOS 16.1 beta version crashed

SkeletonView Environment:

SkeletonView version: 1.25.1 **Xcode version:**13.2.1 Swift version: 5

Attachments:

SkeletonView UIView+Swizzling.swift - Line 21 @objc UIView.skeletonLayoutSubviews() + 21

Fatal Exception: NSGenericException Unable to activate constraint with anchors <NSLayoutDimension:0x280d89440 "_UINavigationBarTitleControl:0x10657df40.height"> and <NSLayoutDimension:0x280d9df80 "UILayoutGuide:0x2821ecc40'TitleViewGuide(0x106450900)'.height"> because they have no common ancestor. Does the constraint or its anchors reference items in different view hierarchies? That's illegal.

Contributor guide

Research direction
Inspect the crash in UIView+Swizzling.swift line 21. The issue is a constraint conflict on iOS 16.1. Check if the skeleton view's layout method adds constraints that reference views from different hierarchies. Look for any recent changes in SkeletonView related to navigation bar title control.
Tech stack
swift
Domain
mobile
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
iOS DevelopmentSwift
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60