You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
URLs in IAM are constructed from plain strings, which makes them vulnerable to easy-to-make mistakes, such as trailing whitespaces. In some cases, such mistakes result in crashes (#8482).
Although it’s not possible to rule out every situation which prevents a successful string-to-URL conversion, certain issues—such as redundant whitespaces in the URL string—can be fixed automatically.
Additionally, the Firebase Console clearly states that image URLs must use the HTTPS scheme. This requirement is not enforced in the SDK, which may lead to inconsistent results, depending on App Transport Security configuration et al., and a bunch of confusion.
The text was updated successfully, but these errors were encountered:
* URL strings in in-app messages are sanitized and, when possible, recovered before they’re used in the `NSURL` initializer
* Added validation for image URLs, which must use the HTTPS scheme, according to the Firebase Console
* Updated `FIRIAMFetchResponseParserTests` to test URL validation and recovery
Feature proposal
URLs in IAM are constructed from plain strings, which makes them vulnerable to easy-to-make mistakes, such as trailing whitespaces. In some cases, such mistakes result in crashes (#8482).
Although it’s not possible to rule out every situation which prevents a successful string-to-URL conversion, certain issues—such as redundant whitespaces in the URL string—can be fixed automatically.
Additionally, the Firebase Console clearly states that image URLs must use the HTTPS scheme. This requirement is not enforced in the SDK, which may lead to inconsistent results, depending on App Transport Security configuration et al., and a bunch of confusion.
The text was updated successfully, but these errors were encountered: