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

Support authentication #1

Closed
jeromegamez opened this issue Jan 9, 2015 · 3 comments
Closed

Support authentication #1

jeromegamez opened this issue Jan 9, 2015 · 3 comments
Assignees
Milestone

Comments

@jeromegamez
Copy link
Member

see https://www.firebase.com/docs/rest/guide/user-auth.html

@jeromegamez jeromegamez added this to the 1.0 milestone Jan 9, 2015
@jeromegamez jeromegamez self-assigned this Jan 10, 2015
@kop
Copy link

kop commented Feb 28, 2015

+1

@jeromegamez jeromegamez changed the title Support user authentication Support authentication Apr 8, 2015
@jeromegamez
Copy link
Member Author

Closed by 50cc8f0.

This was referenced Oct 22, 2018
i3130002 added a commit to i3130002/firebase-php that referenced this issue Jan 30, 2020
Resolves "Fatal error: Uncaught TypeError: Argument 1 passed to Kreait\Firebase\Messaging\Topic::fromValue() must be of the type string, int given, called in /home/public_html/vendor/kreait/firebase-php/src/Firebase/Messaging/AppInstance.php on line 44 and defined in /home/public_html/vendor/kreait/firebase-php/src/Firebase/Messaging/Topic.php:19 Stack trace: #0 /home/public_html/vendor/kreait/firebase-php/src/Firebase/Messaging/AppInstance.php(44): Kreait\Firebase\Messaging\Topic::fromValue(394511638) kreait#1 /home/public_html/TestFiles/1.php(18): Kreait\Firebase\Messaging\AppInstance::fromRawData(Object(Kreait\Firebase\Messaging\RegistrationToken), Array) kreait#2 {main} thrown in /home/public_html/vendor/kreait/firebase-php/src/Firebase/Messaging/Topic.php on line 19"

Happens when subscribed topic happens to be a JSON::Decode Integer
@lock
Copy link

lock bot commented Mar 17, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Mar 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants