Juanpe / Juanpe/SkeletonView

Crash in UIView.skeletonLayoutSubviews() UIView+Swizzling.swift - Line 20

Open
#593 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
12.9k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

Description

Hi, I integrated SkeletonView into my UIKit app, and by using Firebase, we’ve seen multiple crashes reported as coming from your library. We really like how SkeletonView works and looks, so I’d really appreciate your help with this.

My team and I haven’t been able to reproduce the issue ourselves, and I also haven’t found a similar report so far. I understand this may be hard to identify or reproduce, but hopefully the Firebase crash logs will help. Note: 100% of the issues have been reported using an iPad, but this might be a misleading clue because most users use iPads.

Thanks in advance for your support!

What type of issue is this? (place an x in one of the [ ])
  • bug
  • enhancement (feature request)
  • question
  • documentation related
  • discussion
Requirements (place an x in each of the [ ])
  • I've read and understood the Contributing guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
SkeletonView Environment:

SkeletonView version: SPM 1.31.0
Xcode version: 26 & 16
Swift version: 5

Steps to reproduce:
  1. No steps yet, I have not been able to reproduce it, but many of our users have.
Expected result:

No crash.

Actual result:

Crash.

Attachments:

com.snaptypeapp.pro2_issue_6307fecc4bb635901dab33f0416c4961_crash_session_d097ee6af9484619b733949a706aae6a_DNE_0_v2_stacktrace.txt

Image Image Image Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with UIView+Swizzling.swift at line 20 and inspect the attached Firebase crash stack trace, treating the iPad context as a clue rather than a confirmed cause. No reproduction steps or tests are named; done means identifying a reproducible failure or validating a change that prevents the reported crash.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.