All Versions
163
Latest Version
Avg Release Cycle
23 days
Latest Release
-
Changelog History
Page 10
Changelog History
Page 10
-
v4.18.0 Changes
October 29, 2018โจ Enhancements
Kreait\Firebase\Messaging\CloudMessage
: You can now create a new message with a different target from an existing message by using thewithChangedTarget()
method (Documentation).
-
v4.17.1 Changes
October 27, 2018๐ Bugfixes
- โ The signature of an ID Token is now verified even if a prior error occured (thanks @kanoblake for reporting the issue and providing a test case)
โจ Enhancements
- ID Tokens must have a valid "auth_time" claim.
- ๐ป Tokens with an invalid signature now throw a
Firebase\Auth\Token\Exception\InvalidSignature
exception. It extends the previously thrownFirebase\Auth\Token\Exception\InvalidToken
, so existing behaviour doesn't change. - Service Account related errors are now more fine grained.
-
v4.17.0 Changes
September 12, 2018๐ Changes
- When loading a non-existing/invalid service account file, error details are now included.
- โก๏ธ Database rules are now updated with prettified JSON to improve editing them in the web console.
-
v4.16.0 Changes
August 24, 2018๐ Features
- โ Added support for Remote Config Template validation (Documentation)
- โ Added support for working with the Remote Config History (Documentation)
-
v4.15.1 Changes
August 07, 2018๐ Bugfixes
- When on GCP/GCE, the environment was overriding an explicitely injected service account for API request authentication.
- When on GCP/GCE, the environment was overriding an explicitely injected service account for API request authentication.
-
v4.15.0 Changes
August 05, 2018๐ Features
- ๐ง The SDK can now be used configuration-free on Google Cloud Engine.
-
v4.14.0 Changes
August 05, 2018๐ Features
- ๐
Kreait\Firebase\Messaging\CloudMessage
can handle all currently supported types of messages and supersedes the specialized message types.
๐ Deprecations
Kreait\Firebase\Messaging\MessageToTopic::fromArray()
- Use
Kreait\Firebase\Messaging\CloudMessage::fromArray()
- Use
Kreait\Firebase\Messaging\MessageToTopic::create($topic)
- Use
Kreait\Firebase\Messaging\CloudMessage::withTarget('topic', $topic)
- Use
Kreait\Firebase\Messaging\ConditionalMessage::fromArray()
- Use
Kreait\Firebase\Messaging\CloudMessage::fromArray()
- Use
Kreait\Firebase\Messaging\ConditionalMessage::create($condition)
- Use
Kreait\Firebase\Messaging\CloudMessage::withTarget('condition', $condition)
- Use
Kreait\Firebase\Messaging\MessageToRegistrationToken::fromArray()
- Use
Kreait\Firebase\Messaging\CloudMessage::fromArray()
- Use
Kreait\Firebase\Messaging\MessageToRegistrationToken::create($token)
- Use
Kreait\Firebase\Messaging\CloudMessage::withTarget('token', $token)
- Use
- ๐
-
v4.13.3 Changes
July 25, 2018๐ Bugfixes
- 0๏ธโฃ Sanitizing the project ID by default changed the output of the method
\Kreait\Firebase\ServiceAccount::getProjectId()
, so a new method\Kreait\Firebase\ServiceAccount::getSanitizedProjectId()
is now used instead.
- 0๏ธโฃ Sanitizing the project ID by default changed the output of the method
-
v4.13.2 Changes
July 25, 2018๐ Bugfixes
- ๐ง Project IDs that cannot be used for database URIs directly are sanitized when configuring a Service Account (#228)
Non-breaking changes
- When publishing an outdated Remote Config, Firebase previously returned an "OPERATION ABORTED" error,
resulting in a
Kreait\Firebase\Exception\RemoteConfig\OperationAborted
exception. Firebase has changed the error to "VERSION MISMATCH", which now results in aKreait\Firebase\Exception\RemoteConfig\VersionMismatch
exception. The new exception inherits from the old exception, so no code changes are required. - ๐ป A
Kreait\Firebase\Exception\RemoteConfigException
now includes the full error as returned by the Firebase API.
-
v4.13.1 Changes
July 17, 2018