-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIAM Crashing App #12882
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Thank you. I'll provide any information you may need. I'm sure my "approach" to getting to that FIAM trigger and how I manage views at start up are probably part of the problem. |
Thanks for reporting this, @RiverboatGambler. I was able to reproduce the same issue. With this, I'll be raising this to our engineers and see what we can do here. |
Thanks for the report, @RiverboatGambler. This could be related to some recent changes in that class. |
I won't lie - I'm relieved because when it comes to stuff like this because I'm not great at triage. Thanks for all you do! |
Can confirm massive uptick, i use foreground ATT-Preroll and "newer version available" nudges. I just stopped the long running campaigns, just to see if I can prevent that code path from running via server side (temporarily killing the IAM campaign). @rizafran @ncooke3 if you want a permalink to full trace lmk and i can email/dm, but i'm guessing you don't need if you were able to repro
//__49+[FIRIAMDefaultDisplayImpl getViewResourceBundle]_block_invoke (FIRIAMDefaultDisplayImpl.m:70)
#endif // SWIFT_PACKAGE
NSBundle *containingBundle;
NSURL *bundleURL;
// The containing bundle is different whether FIAM is statically or dynamically linked.
for (containingBundle in @[
// Statically linked.
[NSBundle mainBundle],
// Dynamically linked.
[NSBundle bundleForClass:myClass],
// Embedded static framework (zip distribution). |
Is there any update related to this ticket? |
The same issue when we updated to 10.25.0
|
Hi everyone, sincere apologies for the trouble. I'm working on addressing this in #12882. We'll have a fix going out in the Firebase 10.27.0 release. Until then, I recommend downgrading to 10.24.0. |
rolled back to 10.24. issue went away for me. thanks for posting..was losing my mind. |
Description
Please bear with me as I'm not an "expert" bug poster. This issue started happening as soon as I upgraded from Firebase version 10.17.0 to 10.24.0. It also manifests in version 10.25.0
The issue is that my app crashes as soon as it's launched when it tries to display a modal FIAM message. I don't know if the modality has anything to do with things. From some Google searches, it looks like a similar issue may have existed before related to "bundles".
Stack trace from XCode 15.2 (from @implementation FIRIAMDefaultDisplayImpl)
Screenshot of code from XCode:
Reproducing the issue
I can reproduce it in my app by simply triggering an in-app message.
Firebase SDK Version
10.24 or earlier
Xcode Version
15.2
Installation Method
Swift Package Manager
Firebase Product(s)
In-App Messaging
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
Expand
Package.resolved
snippetReplace this line with the contents of your Package.resolved.
If using CocoaPods, the project's Podfile.lock
Expand
Podfile.lock
snippetReplace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered: