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
InAppMessaging bundle is missing #23
Comments
I added this run script to fix the problem. |
Thank you for calling this out @michalciurus! From what I can gather, you more or less found the source of the issue. The framework is searching for Apple recommends using
I will try to fork the firebase-ios-sdk this weekend and test this out, but for now I'd say your script is a decent workaround. |
Follow up -- unfortunately because it's a pre-built binary, The solutions as I see it:
I think 2 is the safer solution, since it doesn't rely on names/file structures which may change. In the meantime, I created a SwiftPM pitch to allow for including resources directly in the main bundle, maybe it will get some traction: |
As per above discussion, I made the following changes:
PR: #25 |
Thank you @akaffenberger for such a swifty turnaround! Me and our team really appreciate the work you're doing. |
8.15.0 - [Firebase/InAppMessaging][I-IAM400009] Display ran into error for message 3978956120715808093: Error Domain=com.firebase.inappmessaging.display Code=1 "(null)" UserInfo={message=resource bundle is missing}
I can't get the in app messages to work.
How are
.bundles
working with SPM and Firebase?Firebase seems to be using, for getting the resources for
InAppMessaging
Correct me if I'm wrong: SPM puts all the resources into the main app bundle, but
mainBundle
called from.xcframework
won't be the app bundle, it'll be the framework bundle, hence it can't find the needed resources. That's as far as I've gone with my investigation.I'm trying to understand how to fix this issue as we really enjoy using this mirror. Could it have regressed? Or maybe I configured something incorrectly.
The text was updated successfully, but these errors were encountered: