First steps
Courses
User Data
- Responsive Email Editor Review
- Designing your email
- Creating Synchronized Modules
- Setting Up Responsive Email Design
- Setting Up Smart Containers
- Creating a Gmail Promotions Annotation
- Adding The Rollover Effect
- Adding Anchor Links
- Module Library
- Adding a Table to an Email
- Adding Custom Fonts
- Creating CTA Button
- Working with Images
- Creating Timer
- Using AI in the Email Editor
- Messenger Protocol Support in Email Clients and Platforms
Omnichannel
- SDK for Mobile Apps
- Managing Mobile SDK Access Keys
- Connecting Mobile App
- Creating and Uploading a Firebase Key
- Creating Mobile Push Messages
- Setting Up Delivery and Clicks Analytics
- Deep Link Types
- Scheduled Mobile Push Message
- Sending Test Messages from the Event Debug View
- Error Codes for Mob Push Notifications
- Setting Up Widgets for Your Site
- Widgets Gamification
- Widget Calling
- Setting Up Locations for the Widget Calling Rules
- Storing data from widgets to contact fields
- Using Annoyance Safeguard
- Actions After Subscription
- Replacing Double Opt-In System Workflow
- Creating Pop-ups via Google Tag Manager or WordPress
- Sending Yespo Widget Events to Google Analytics
- Using A/B Tests for Widgets
- Collecting Contact Information Using Request Forms
Automation
- Building and Editing Workflows
- Configuring Workflow Start/Stop Conditions
- Start Block
- Popular Blocks
- Message Blocks
- Using One from Many Message Block
- Contact Blocks
- Conditions Blocks
- Other Blocks
- Message to Segment Blocks
- Time Blocks
- Advanced Workflow Block Parameters
- Setting Up Allowed Send Time
- Using Workflow Launch History
- Webhook Workflows
- Workflow Troubleshooting
- Double Opt-In
- Welcome Сampaign
- Welcome Series Segmented by Category
- Launching a Workflow After a Contact Import
- Regular Workflow for a Segment
- Birthday Campaign
- Linking Workflow to the Button
- Using Variables from Order in Workflow
- Collecting Order Feedback
- Customer Reactivation
- Using A/B Tests In Workflows
- Sending Extra Campaigns
- Sending Reminders at the Time Specified by the User
- Sending Campaign to Those Who Did Not Open the Previous One
Personalization
Analytics
- Email Campaign Report
- Web Push Campaign Report
- Viber Campaign Report
- Mobile Push Campaign Report
- App Inbox Campaign Report
- Telegram Campaign Report
- In-App Report
- Widget Report
- Triggered Campaign Report
- AMP Campaign Report
- SMS Campaign Report
- Multilingual Campaign Report
- Setting up UTM Tags
- Revenue from Campaigns
- Tracking Campaign Performance in Google Analytics 4
- Message Analytics
Multilanguage Campaigns
Events and Behaviour Tracking
Recommendations
API
Security and Compliance
Error Codes for Mob Push Notifications
In mobile application development, errors and issues are inevitable, especially when dealing with complex services like Firebase and APNS.
This article provides a comprehensive guide to understanding common error scenarios, their causes, and actionable solutions.
| Error | Possible Cause | Troubleshooting |
|---|---|---|
| Device token not registered | Invalid token. When using Firebase for iOS and Android, APN certificates added to Firebase may expire or not be generated for the required environment. When adding an Apple application to an FCM project, ensure that certificates are uploaded separately for each environment. It is possible that the production certificate is being used for the development environment, or vice versa. | Check the certificate's validity and if it is used in the proper environment. |
| The authenticated sender ID is different from the sender ID for the registration token | A problem with the Firebase service account. | Try to expand permissions in the service account. |
| The token was generated in one Firebase project, but the push attempt was made from another. It is possible that a token from the test environment is being used in production, or vice versa. | Ensure the proper use of tokens. | |
| MOB_PUSH_GENERAL_ERROR | The error has no description from the APNS service and may indicate a failure on the APNS service side. | Contact our support team for a detailed analysis. |
| No more information is available about this error | No information about the error. | Contact our support team for a detailed analysis. |
| Request parameters were invalid | APNS was selected for push notifications in the admin panel, but the SDK is set up to use FCM tokens, or vice versa. |
Solution Options:
Or,
|
| InvalidProviderToken | The APN authentication token used for sending notifications via APN might have been revoked in the Apple Developer Center. | Create a new APNs Auth Key. |
| Incorrect setup of the p8 certificate. | Check the certificate settings. | |
| badDeviceToken | The error occurs when APNS tokens generated for the Sandbox environment are used in production, or tokens generated for production are used in the test environment. |
Contact our support team to switch the Sandbox configuration to true. When using APN for iOS, it is recommended to have two applications:
|
