Could not find mobile settings for push notifications

[Mario_Ghersi]

We noticed there was an attempt to send a push notification in a Backendless application where you are registered as a developer. You can find the details about the app below:

Application name: TargettAcceso
Application ID: 147F3E51-266A-AAC4-FF2B-DFE9F84FD200

Unfortunately, the push notification could not be delivered because some required configuration is missing in your backend. Please make sure to configure the following:

• Android server keys (for Android push notifications)
• iOS Certificate(s) (for iOS push notifications).

Any idea why is not working and still receiving this messages.
I’d tested in a different App and it is working properly but this old setup stop it.

Thanks Mario

[viktor.liablin]

Hello @Mario_Ghersi

I’d tested in a different App and it is working properly but this old setup stop it.

I didn’t quite understand. Can you please explain a little? You use the same settings in other app and they work fine in other applications, but in the TargettAcceso app these settings don’t work?

Regards

[Mario_Ghersi]

Yes the Test App (SMSApp) works fine but I need to continue using the notifications with the upgrade in my production app (Targett Acceso). I found the message at Firebase the token in not longer available I need to create a new one. Study how to do it now.

[Karyna]

Hello, @Mario_Ghersi

It looks like the issue is with the push configuration in your production app Targett Acceso. The error message means that the app is missing valid Android server keys or iOS certificates. Since Firebase shows the token is no longer available, you will need to generate a new token/key in Firebase and then update your Backendless app settings with it.

Kind regards,
Karyna

[Mario_Ghersi]

Hi Karyna

The new Private Key is uploaded since yesterday but still not working properly can you check from for side if the message are sent ?

Thanks, Mario

[Mario_Ghersi]

Taking about the IOS is not working an d when I try to upload the production kay give me this error.

The SANDBOX and the PRODUCTION should be different.
Any ideas? Thanks, Mario

[Inna_Shkolnaya]

Hello @Mario_Ghersi

Am I correct in understanding that you are trying to add different certificates for one channel?
One channel can only have one certificate.

Regards,
Inna

[Mario_Ghersi]

OK, for iPhone clear the SANDBOX and add the PRODUCTION.

Clear the App download the production app from the Apple Store. The device Id still the same, but not receiving the notification. The Send message is green.

Thanks, Mario

[Viktor_Mudrevsky]

Hi @Mario_Ghersi

I can see in our logs that push messages are being sent, but one device appears as invalid:
deviceId = 3E802E4C-CCD0-43B2-86B9-1FD500E31D81.

Could you please confirm:

• Are all your push settings (keys, certificates) configured correctly now?
• How exactly are you sending the push (from the console or via API)? If from the console, which device are you targeting?
• Please check the message status using this guide: Get Message Status.
• Try sending the push to another device.
• Try re-registering the device.
• In the other app where pushes work, which device are you sending to — the same one or a different one?
• Does the issue happen only on iOS or also on Android?

Regards,
Viktor

[Mario_Ghersi]

Hi Viktor

For iPhone yes the device Id id the one you said is invalid and for Android is “2fb2adb9cde6dd46”

The Templates are at the console and yes I’m using the console for test.

1. The keys and certificates are new and should be correct but something still wrong.

2. From Console and the targets are the ones descriptor 1 iPhone and 1 Android

3. I will see how to check the Get Message Status at the console…

4. OK I will use the UI Bulder and use the webpage.

5. I do it give me same deviceIds. Thats OK ?

6. The Test App SMSApp using the console everything OK. All update and same Android phone.

Thanks, Mario
PD I will continue testing in Monday.

[Volodymyr_Ialovyi]

Hello @Mario_Ghersi

Thank you for the detailed updates and screenshots throughout your troubleshooting process. Let’s systematically analyze both applications and create a clear testing plan for Monday.

Current Configuration Analysis

TargettAcceso App (147F3E51-266A-AAC4-FF2B-DFE9F84FD200):

Settings:

• Android: targett-acceso-private-key (Backendless Console → Manage → App Settings → Mobile → Android)
• iOS: push_certificate.p12 (Backendless Console → Manage → App Settings → Mobile → iOS)

Permissions:

• Channel: default (Backendless Console → Messaging Channels → default → Permissions → Role Permissions) = Publish/Subscribe status: DENY for ManagementUser, NotAuthenticatedUser, and SocialUser

Current Templates:

• TestVisita: 1 recipient (deviceId = ‘2fb…’ → Android, channelName = default, objectId = BA7B4B3F-0D5A-4958-9F12-7FC739DEF72A)
• iPhoneTest: 1 recipient (deviceId = ‘3E802E4C…’ → iOS, channelName = default, objectId = 8EAF1BB7-2B2E-4435-8BC7-08DC384D8231)

---

SMSApp (C4BBAE0D-39FF-433D-AED7-5740B4A6E863) - Working Configuration:

Settings:

• Android: smsapp-private-key
• iOS: empty

Permissions:

• Channel: default = Publish/Subscribe status: DENY for AutomationUser and ManagementUser

Templates:

• TestTemplate: 1 recipient (deviceId = ‘2fb…’ → Android, channelName = default, objectId = E22A67A2-BB56-4602-9D54-A302D6F98944)

Recommended Testing Steps for Monday

For each template test, please follow this sequence:

1. Select Template (Backendless Console → Push Notifications → Push Templates → [Template Name])
2. Send Push using either:

• Console method
• API method

3. Capture API Response:

{  
  "status": "scheduled" | "failed",  
  "messageId": "<messageId>"  
}

4. Check Message Status using Get Message Status API:

{  
  "status": "failed" | "published" | "scheduled" | "cancelled" | "unknown",  
  "messageId": "value",  
  "errorMessage": "value"  
}

5. Record Device Reception: Note whether the push was received on the target device.

Key Questions for Investigation

1. Permission Issue: Why are permissions set to DENY in TargettAcceso? This might be blocking message delivery.
2. Device Registration: Since the iOS device shows as “invalid,” please try re-registering IOS device with deviceId = 3E802E4C-CCD0-43B2-86B9-1FD500E31D81 in TargettAcceso.

Please run through these steps systematically on Monday and share the API responses and message status results. This will help us pinpoint exactly where the delivery is failing in TargettAcceso.

Regards,
Volodymyr

[Mario_Ghersi]

Hi Volodymyr

I was working in other issues now back again with the push notification problem.

1. Add new Android credentials
2. Check the software with the documentation
3. sent to this devices deviceId = ‘2fb2adb9cde6dd46’ the message is green but never arrive to the phone.

Where I can check the status of the message using the console?

Thanks, Mario

[Mario_Ghersi]

Finally is working

implementation group: ‘com.backendless’, name: ‘android-client-sdk’, version: ‘7.0.9’

Thanks, Mario