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
Reopening #2816 - I cannot receive test messages on device or simulator.
Steps to reproduce:
Add the following to your Podfile:
pod 'Firebase'
pod 'Firebase/InAppMessagingDisplay'
pod 'Firebase/Analytics'
Run pod install
Build and run the app in the simulator or on a device.
Open Firebase Console and create a new In-App Messaging campaign with style: Modal.
Under options select Test on Device, add your InstanceID, and click Test.
Background the running app, then open it again.
The following error is logged to the Xcode console:
2019-09-19 15:17:02.421473+0200 My App[6754:458265] 5.20.0 - [Firebase/InAppMessaging][I-IAM130004] Failed restful api request to fetch in-app messages: seeing http status code as 400 with body as {
"error": {
"code": 400,
"message": "Request contains an invalid argument.",
"status": "INVALID_ARGUMENT"
}
}
Relevant Code:
None
The text was updated successfully, but these errors were encountered:
@christibbs where can we follow progress on this issue in the InstanceID SDK?
I've noticed that this problem only occurs when I update from a previous version of my app with a different version number. If I implement InAppMessaging without updating the version or build numbers, or do a clean install, everything works as expected.
@pimnijman thanks for the additional context. The InstanceID work is complete, we have to do some work on our end to integrate. This should happen in a near-term upcoming release, I'll close this when the work is done.
[READ] Step 1: Are you in the right place?
yes
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
Reopening #2816 - I cannot receive test messages on device or simulator.
Steps to reproduce:
Add the following to your Podfile:
pod install
InstanceID
, and click Test.The following error is logged to the Xcode console:
Relevant Code:
None
The text was updated successfully, but these errors were encountered: