-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[iOS] App Crash when using Baidumap with FirebaseAnalytics #8505
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
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Can you share the full stack trace? If you're able to reproduce it with Xcode's debugging tools attached, you should be able to get the full stack trace by typing |
Full stack trace:
Did you try to run my reproduce project? |
This crash could be the result of BaiduMapKit embedding a version of nanopb that is incompatible with the version used by Firebase. |
Hi @paulb777 Thanks, |
If BaiduMapKit is using nanopb via a CocoaPod without using the nanopb CocoaPod, there's not much we can do on the Firebase side. They should either use the nanopb CocoaPod with matching preprocessor defines as Firebase or rename all the nanopb public symbols in their internal copy. |
Yes, I see. But that difficult to request an update from BaiduMapKit. |
Closing since this seems to be a BaiduMapKit issue and not clear what we can do from Firebase. |
Uh oh!
There was an error while loading. Please reload this page.
Step 0: Are you in the right place?
file a Github issue.
with the
firebase
tag.google group.
of the above categories, reach out to
Firebase Support.
this repository, please delete this section.
[REQUIRED] Step 1: Describe your environment
CocoaPods
][REQUIRED] Step 2: Describe the problem
App crash

Steps to reproduce:
var options = FirebaseOptions.defaultOptions()
FirebaseApp.configure(options: options!)
I also reproduce crash from
Reproduce project:
https://drive.google.com/file/d/15p8F8kQxRfkKdC8Rdag4Od-Q1KQ85zEK/view?usp=sharing
The text was updated successfully, but these errors were encountered: