Your push notification delivery failure after FCM credential rotation requires systematic verification across three critical areas: FCM credential configuration, Sender ID/API key validation, and device token monitoring.
FCM Credential Configuration in AEC 2022:
FCM credentials must be updated in THREE separate locations for proper notification delivery:
- Integration Hub Configuration:
Admin Console > Integration Hub > Mobile Integrations > Firebase Cloud Messaging
- Server Key (Legacy): [Your new FCM Server Key]
- Sender ID: [Your new FCM Sender ID]
- Project ID: [Your Firebase Project ID]
- Click “Test Connection” to verify credentials are accepted
- Push Notification Service:
Admin Console > Mobile Services > Push Notification Service > Provider Settings
- Provider: Firebase Cloud Messaging
- API Key: [Same FCM Server Key from above]
- Application Package Names: Verify iOS bundle ID and Android package name
- Certificate Status: Should show “Valid” after update
- Mobile App Configuration:
Admin Console > Mobile Apps > [Your Sales App] > Settings > Push Configuration
- FCM Integration: Enabled
- Sender ID: [Must match Firebase console exactly]
- Service Account: Upload new service account JSON file from Firebase
- Priority: High (for real-time notifications)
After updating all three locations, restart the Push Notification Service:
Mobile Services > Push Notification Service > Actions > Restart Service
Wait 2-3 minutes for service to fully restart before testing.
Sender ID and API Key Validation:
Verify credential accuracy with these specific checks:
- Firebase Console Verification:
- Log into Firebase Console > Project Settings > Cloud Messaging
- Confirm Server Key matches what you entered in AEC
- Verify Sender ID (numeric value) matches exactly
- Check that Cloud Messaging API is ENABLED (common issue after credential rotation)
- API Key Permissions:
Ensure your FCM Server Key has correct permissions:
- Firebase Cloud Messaging API: Enabled
- IP Restrictions: None (or whitelist AEC notification service IPs)
- Application Restrictions: None (or specify your mobile app package names)
- Test Credential Validity:
Use Integration Hub’s built-in test tool:
Integration Hub > Mobile Integrations > FCM > Test Configuration
- Send test notification to a specific device token
- Review response code (should be 200 OK)
- Check for authentication errors in the response
If test fails with 401 Unauthorized, your API key is incorrect or expired.
If test fails with 403 Forbidden, check IP restrictions in Firebase.
Device Token Monitoring and Management:
After credential rotation, device tokens often need revalidation:
- Run Token Validation Job:
Mobile Integration > Device Registry > Actions > Validate All Tokens
This queries FCM to check token validity:
- Valid tokens: Remain in registry
- Invalid tokens: Marked for re-registration
- Expired tokens: Automatically purged
Validation typically takes 5-10 minutes for large device populations.
- Force Token Refresh:
For immediate resolution, push a token refresh command:
Mobile Integration > Device Registry > Actions > Broadcast Token Refresh
This sends a silent push to all devices instructing them to re-register.
Alternatively, communicate to users:
“Please force-close and reopen the Sales App to restore push notifications”
- Monitor Token Registration:
Mobile Integration > Device Registry > Registration Activity
Filter by: Last 24 hours
You should see devices re-registering after the refresh command.
Healthy registration rate: 70%+ of active users within 24 hours.
- Set Up Token Monitoring Alerts:
Create alert rule for low token registration:
Mobile Integration > Alerts > New Rule
- Condition: Active tokens < 80% of expected user count
- Check Frequency: Every 6 hours
- Notification: Email to mobile_app_admin
Troubleshooting Checklist:
If notifications still don’t deliver after above steps:
- Check AEC notification service logs:
Admin Console > System Logs > Notification Service
Filter by: FCM, Last 24 hours
Look for authentication errors or connection timeouts
- Verify network connectivity:
Ensure AEC can reach FCM endpoints:
- Review FCM quota limits:
Firebase Console > Usage and Billing
Verify you haven’t exceeded daily message quota
- Test with specific device token:
Mobile Integration > Tools > Send Test Notification
Enter a known valid device token
Send test message and check device immediately
- Check app permissions:
Verify mobile app still has notification permissions enabled on user devices
iOS: Settings > [App Name] > Notifications
Android: Settings > Apps > [App Name] > Notifications
Additional Configuration for AEC 2022:
- Enable FCM v1 API (Recommended):
AEC 2022 supports both legacy and v1 FCM APIs. The v1 API is more secure:
Integration Hub > FCM Settings > API Version > Select “v1 (OAuth 2.0)”
Upload service account JSON file from Firebase
This requires re-registering all device tokens but provides better reliability
- Configure Retry Logic:
Push Notification Service > Advanced Settings
- Retry Attempts: 3
- Retry Delay: Exponential backoff (1s, 2s, 4s)
- Fallback Action: Log failed notifications for manual review
- Set Up Notification Logging:
Enable detailed logging for troubleshooting:
Mobile Services > Logging > Enable Debug Mode
Log Level: INFO (or DEBUG for detailed troubleshooting)
Log Retention: 7 days
After implementing these changes, conduct end-to-end testing:
- Send test notification from AEC to your device
- Verify notification appears within 10 seconds
- Check Integration Hub logs for successful delivery confirmation
- Monitor Device Registry for any token registration issues
If issues persist after all validation steps, the problem may be with Firebase project configuration rather than AEC. Check Firebase Console > Cloud Messaging for any service disruptions or project-level restrictions that may have been applied during credential rotation.