Skip to content
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

Firebase initialisation problem #2

Closed
cemozturk opened this issue Nov 12, 2016 · 2 comments
Closed

Firebase initialisation problem #2

cemozturk opened this issue Nov 12, 2016 · 2 comments

Comments

@cemozturk
Copy link

cemozturk commented Nov 12, 2016

Hi,

In your papers, you said just put the GoogleService-Info.plist file at proper location and call for desired functions to initalize the Firebase connection and play with it.

When i tried

	Firebase.Messaging.FirebaseMessaging.TokenReceived  = OnTokenReceived;
	Firebase.Messaging.FirebaseMessaging.MessageReceived  = OnMessageReceived;

it says,

The project's Bundle ID is inconsistent with either the Bundle ID in 'GoogleService-Info.plist', or the Bundle ID in the options if you are using a customized options. To ensure that everything can be configured correctly, you may need to make the Bundle IDs consistent. To continue with this plist file, you may change your app's bundle identifier to '__FIRAPP_DEFAULT'. Or you can download a new configuration file that matches your bundle identifier from https://console.firebase.google.com/ and replace the current one.

I debugged the logs and saw that your initalizing process is not waiting for Firebase to fully init. ( reading google-plist file, connecting to FCM etc.. )

When i wait for 10 seconds and trigger Firebase.Messaging.FirebaseMessaging.TokenReceived, i can get the token.

Please give us a proper create/build/init function with proper result delegate.

@stewartmiles
Copy link
Contributor

The error about the inconsistent bundle ID does not affect the behavior of Firebase Messaging, though it's a bug we're working on fixing right now, see https://groups.google.com/d/msg/firebase-talk/HXSy9IIPEVY/_GT12d39CQAJ .

If I understand you correctly, the delay you see a consistent regarding the reception of the registration token? Since this is an asynchronous process that depends upon network conditions you're not guaranteed to receive a token immediately after startup.

Also, are you able to reproduce this problem with our sample application?

Cheers,
Stewart

@stewartmiles
Copy link
Contributor

I'm pleased to announce that we released:

  • Firebase C SDK 2.1.0 (release notes here, download here)
  • Firebase Unity SDK 1.1.0 (release notes here, download here)

I believe this should resolve your issue. If not, please let us know and we'll take a look.

Cheers,
Stewart

stewartmiles pushed a commit to stewartmiles/quickstart-unity that referenced this issue Feb 21, 2017
@firebase firebase locked and limited conversation to collaborators Oct 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants