Pinpoint Notifications always use APNs Sandbox channel about amplify-flutter HOT 11 CLOSED

Well that was a quick fix :D Thanks a lot for the help! It would be great if this was mentioned in the documentation though!

from amplify-flutter.

@Niklas-Sommer thanks for taking the time to raise this issue. Amplify will decide the appropriate channel based on the application's compiled environment and if it is running on debug mode it registers the endpoint as APNs Sandbox . While we investigate, could you please verify whether the release app is running in debug mode using zDebugMode similar to the code snippet below:

if (zDebugMode) {
  print('running on debug mode');
}

from amplify-flutter.

I did test that and it is indeed running in release mode. As stated above it even gets registered in pinpoint as an APNs endpoint but I still only receive push notifications when I send it to the APNs Sandbox channel. That's the error I get when sending a test message with the pinpoint console to the the APNs channel:

Request Id 68 : [<DEVICE_TOKEN>: PERMANENT_FAILURE {"errorMessage":"Unregistered or expired token","channelType":"APNS","pushProviderStatusCode":"400","pushProviderError":"BadDeviceToken","pushProviderResponse":"{"reason":"BadDeviceToken"}"}]

from amplify-flutter.

@Niklas-Sommer thank you for providing these details. we will look into this issue and get back to you with any updates.

from amplify-flutter.

@Niklas-Sommer when running flutter run command do you use any command line options such as --dart-define to set environment valriables?

from amplify-flutter.

I am launching my flutter project from VS Code in release mode so I didn't specify any. Not sure which arguments vs code passes when launching.

from amplify-flutter.

Just tried running from the command line with

flutter run --release

Still does not work

from amplify-flutter.

@Niklas-Sommer sending notifications directly through the Pinpoint console to both APNS and APNS_SANDBOX channels with tokens and only APNS_SANDBOX is successfully delivered indicates that the device token received from APNs is for the sandbox environment.
Would you please verify that the APNS SSL certificate is for Sandbox & Production?

If the certificate is for Sandbox only then you may need to generate a certificate for Sandbox and Production and update the Pinpoint project to use the new certificate.

from amplify-flutter.

I am not quite sure where on apple developer you navigated to find what is shown on your screenshot but I checked
AppleDeveloper->Identifiers->MYAPP->Push Notifications->Edit
and can see that I have a production SSL certificate. No development certificate.

I also checked in my pinpoint project and that looks like this:

Were you not able to reproduce this issue by just creating a basic flutter project with amplify according to the documentation?

from amplify-flutter.

Hi @Niklas-Sommer, I've been able to reproduce this on a fresh Amplify Flutter app.

I'm still investigating the root cause, but wanted to update you in the meantime.

I'll provide more information when I have it.

from amplify-flutter.

Hi @Niklas-Sommer, it appears running the app with the release flag is not sufficient for iOS to setup the correct production environment. I was able to successfully receive a APNs (non-sandbox) push notification through both of these methods:

• Build the Flutter iOS via .ipa,
  • Using this command flutter build ipa --release --export-method ad-hoc
  • Plug in your physical device and drag & drop the .ipa file onto the device
  • Here is a relevant stack overflow
• Test App via TestFlight

For both scenarios ensure you don't have a pre-existing version of the app already installed. And ensure you have a method of retrieving the device id.

Note: when the app is built this way APNs Sandbox push notifications will throw a similar error to what you were getting before.

Let us know if this resolves the issue for you or if you have additional questions.

from amplify-flutter.