- Newest
- Most votes
- Most comments
nevermind it was a problem with env variables. I followed following and added the variable in build command https://docs.amplify.aws/nextjs/deploy-and-host/fullstack-branching/secrets-and-vars/
To send push notifications to iOS and macOS devices, you need to use the Apple Push Notification service (APNs). For web push notifications to Safari browsers on macOS, you would specifically use APNs web push capabilities.
The issue you're experiencing where notifications work locally but not on your hosted Amplify app could be related to several factors:
-
Credentials and Authorization: When deploying on Amplify, you need to ensure that your application has the proper credentials to communicate with push notification services. For APNs, you need an encryption key, key ID, and provider certificate from Apple. For FCM, you need credentials from the Firebase console.
-
SSL/TLS Configuration: Push notification services like APNs and FCM require secure connections. If there's an SSL verification issue when your Amplify-hosted app tries to connect to these services, notifications would fail.
-
Environment Variables: Your local environment might have environment variables or configuration settings that aren't properly set in your Amplify environment.
To resolve this issue:
- Verify that your Amplify environment has the correct environment variables and configuration for your push notification services.
- Check if there are any errors in your Amplify logs related to outbound connections to FCM or APNs.
- Ensure that your application in Amplify has the necessary permissions to make outbound HTTPS calls.
If you're using the VAPID approach for web push notifications, make sure your VAPID keys are properly configured in your Amplify environment. For Safari web push notifications specifically, you'll need to follow Apple's requirements for web push which may differ from the standard VAPID implementation.
Amplify doesn't typically require you to manually add SSL certificate chains for outbound connections, as it should handle HTTPS connections properly by default. The issue is more likely related to configuration or credentials rather than SSL verification.
Sources
Receiving push notifications in your application - AWS End User Messaging Push
Sending mobile push notifications with Amazon SNS - Amazon Simple Notification Service
Amazon Pinpoint push notifications - Amazon Pinpoint
Getting started with AWS End User Messaging Push - AWS End User Messaging Push
answered a year ago
Relevant content
asked 3 years ago
asked 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 months ago

since i am not using SNS or pinpoint, it cannot be permissions, application is simply making an outbound API call. The same env variables are configured in local and Amplify.