Apple recently introduced the same bundle identifier feature.
We are supporting two different platforms: MacOS build via MacCatalyst and iPhone/iPad
What is the best practice for the Crashlytics/Firebase setup when using the same bundle identifier?
Best practice for a Firebase setup when the macOS and iOS apps must have the same bundle ID is to put them into two separate Firebase projects. Attempting to include them in the same Firebase projects will cause problems (and you can't have two separate apps in the same Firebase project with the same bundle ID).
thanks @kevinkokomani ! Could you please elaborate what kind of problems it will cause?
For sure - assuming the actions you take are as follows:
The crashes will stop reporting from your iOS app and will only report from your macOS app, or vice versa if you added the macOS app first. This is due to the requirement of the bundle identifier being unique on a per-project basis.
Thanks for your answer. As Apple is promoting the unified bundle ID a lot, are there plans to also offer a unified GoogleService.plist on the Firebase platform?
One more thing I am curious about, we only talked about the implications on Crashlytics, does using the same GoogleService.plist also have affects on other event reporting services or for example RemoteConfig?
We're working on our Apple platforms unification story across all Firebase components, but don't have anything ready to announce at this time.
@kevinkokomani I ran into this problem by adding tvOS support to an existing iOS project, both sharing the same bundle identifier and GoogleServices-Info.plist. Now it's just report crashes for the tvOS app. Is there any way to "fix" the reporting so I can use the existing project for iOS again and properly add the tvOS project?
@mundue see this comment.
Most helpful comment
We're working on our Apple platforms unification story across all Firebase components, but don't have anything ready to announce at this time.