blog/push-v3-new-cloud/

[giscus[bot]]

blog/push-v3-new-cloud/

Codename One Push V3 adds typed messages, managed credentials, segmentation, analytics, and Surface updates. Existing push apps should test the new cloud endpoint before next week's cutover.

https://www.codenameone.com/blog/push-v3-new-cloud/

[DurankGts]

hi , In trying to migrate my old server push to this new. Your push you said that just update de url

Push notifications should be application infrastructure, not a pile of expiring certificates and provider-specific JSON.

This week we merged Push V3 into the Codename One core and completed its new cloud implementation. It gives an application a typed message model, managed provider credentials, subscriptions, server-side segments, campaigns, analytics, and a direct path into Surfaces.

There is also one thing every existing push developer should do now:

Change the push service URL from https://push.codenameone.com to https://cloud.codenameone.com and send a real notification through your existing code.

Next week we plan to bring down the old push service and direct push.codenameone.com traffic to the new implementation. The compatibility endpoint accepts the existing request format, so existing code should keep working. It is still a completely new server, and “should” is not a test result. Please test before the cutover while both routes are easy to compare.

I update de url but your push server
return
{"error":"credential URL returned HTTP 404"}

I continue using the same parameter that old push.

[DurankGts]

I need support how to keep my production apps receiving push notifications?

[DurankGts]

when I pasted the google-service.json

your server return Error http 400

[DurankGts]

why you have here different url than your initial post?

[DurankGts]

could you tell me what is this field?

this my old server push method to send a push to my production app.

public static FCMResponse sendpush(String urlCn1Pn, String token, String device, String email, String type, String message, String auth, String production, String certPass, String urlCert) throws IOException {
    String methodName = "sendPush()";
    String url = (urlCn1Pn != null && !urlCn1Pn.trim().isEmpty()) ? urlCn1Pn : "[https://cloud.codenameone.com/api/v3/push/messages](https://cloud.codenameone.com/api/v3/push/messages)";
    int code = 0;
    StringBuilder result = null;

    try {
        URL obj = new URL(url);
        HttpsURLConnection con = (HttpsURLConnection) obj.openConnection();

        con.setRequestMethod("POST");
        con.setRequestProperty("User-Agent", USER_AGENT);
        con.setRequestProperty("Accept-Language", "en-US,en;q=0.5");
        con.setRequestProperty(CONTENT_TYPE, "application/x-www-form-urlencoded");

        String query = "token="         + URLEncoder.encode(token, "UTF-8")
                + "&device="        + URLEncoder.encode(device, "UTF-8")
                + "&type="          + URLEncoder.encode(type, "UTF-8")
                + "&auth="          + URLEncoder.encode(auth, "UTF-8")
                + "&certPassword="  + URLEncoder.encode(certPass, "UTF-8")
                + "&cert="          + URLEncoder.encode(urlCert, "UTF-8")
                + "&body="          + URLEncoder.encode(message, "UTF-8")
                + "&production="    + URLEncoder.encode(production, "UTF-8");

        con.setDoOutput(true);
        try (DataOutputStream wr = new DataOutputStream(con.getOutputStream())) {
            wr.write(query.getBytes("UTF-8"));
            wr.flush();
        }

        code = con.getResponseCode();
        InputStream is = (code >= 200 && code < 400) ? con.getInputStream() : con.getErrorStream();

        if (is != null) {
            try (BufferedReader in = new BufferedReader(new InputStreamReader(is, "UTF-8"))) {
                String inputLine;
                result = new StringBuilder();
                while ((inputLine = in.readLine()) != null) {
                    result.append(inputLine);
                }
            }
        }

        WsLog.i(TAG, methodName + "->response  :[" + code + "]" + (result != null ? result.toString() : ""));
    } catch (IOException io) {
        WsLog.e(TAG, methodName + "->ErrorIo  :" + io.toString());
        return null;
    } catch (IllegalStateException is) {
        WsLog.e(TAG, methodName + "->ErrorIs  :" + is.toString());
        return null;
    }

    return new FCMResponse(code, result != null ? result.toString() : "");
}

[DurankGts]

you have a problem when I pasted in android side the credentials

I pressed save Firebase Cloud Messaging credential

perfect but when I refresh the console page or go for example to builds and return to Push the config is losed

[shai-almog]

The Java method you posted uses the classic form-encoded API. For that method, set urlCn1Pn to:

"https://cloud.codenameone.com/push/push"

Keep the existing form parameters. Use the plain URL string, without Markdown brackets or parentheses. /api/v3/push/messages is a separate JSON API and can't accept that form request.

The credential URL returned HTTP 404 response means the server couldn’t retrieve the URL supplied in auth or cert. Check that it remains accessible and hasn’t expired. For Firebase, auth can also contain the complete service-account JSON directly.

The Firebase credential must be the private-key JSON from Firebase Project settings → Service accounts → Generate new private key. Android’s google-services.json is application configuration and can't authenticate server sends.

The Console credential-status display has also been updated. Refresh the page and check Configured/Ready for the same selected application. Saved credential fields remain blank intentionally; their contents aren’t returned to the browser.

If you choose V3 later, create its server key under Account → Server API keys and use the application UUID under Push → Overview → Server API as appId.

[DurankGts]

you must specify in your developer Guide more clear. The AppId is the Client binding in the push ->overview? this not the mobile app package name?

The Console credential-status display has also been updated. Refresh the page and check Configured/Ready for the same selected application. Saved credential fields remain blank intentionally; their contents aren’t returned to the browser.

respect this issue. I pasted an configure/Ready is appear but i think that you must create a Way to user that push is configure althought you don't want creat by security issue. Set some label ready...

[DurankGts]

I think that you must create more clear documetation how to configure push in you console.

https://www.codenameone.com/developer-guide/push-notifications/

For example. I'm trying to configure ios side but you reject the key .p8 file that isn't a JSON. There isn't documentation related with this JSON. I use IA to solve the issue.

I created my own Json with this structure but in your documentation don't said nothing

{
"teamId": "TEAM_ID",
"keyId": "KEY_ID",
"topic": "com.tuempresa.appdos",
"privateKey": "-----BEGIN PRIVATE KEY-----\nMIGTAgEAMBMGByqGSM49AgEGCCqGSM49AwEHBHkwdwIBAQQg...\n-----END PRIVATE KEY-----"
}

Sincerilly it'very dificult to configure Push notification V3 in you console because there isn't clear documentation step by step.

[DurankGts]

this dialog

is very dificult to select other created application in windows

[DurankGts]

Implementing your new push server this response is generated by you server

{"timestamp":"2026-09-30T18:21:31.574+00:00","status":406,"error":"Not Acceptable","path":"/api/v3/push/messages"}

Could you explain me?

[DurankGts]

this my method

public static FCMResponse sendpush(String urlCn1Pn, String serverApiKey, String appId, String provider, String token, String title, String message) throws IOException {
        String methodName = "sendPush()";
        String url = (urlCn1Pn != null && !urlCn1Pn.trim().isEmpty()) ? urlCn1Pn : DEFAULT_URL;
        int code = 0;
        StringBuilder result = new StringBuilder();

        try {
            URL obj = new URL(url);
            HttpsURLConnection con = (HttpsURLConnection) obj.openConnection();

            // Configuración de cabeceras HTTP para Push v3
            con.setRequestMethod("POST");
            con.setRequestProperty("Authorization", "Bearer " + serverApiKey);
            con.setRequestProperty("Content-Type", "application/json; charset=UTF-8");
            con.setRequestProperty("Accept", "*/*");
            con.setRequestProperty("User-Agent", "Mozilla/5.0 (Windows NT 10.0; Win64; x64) CN1PushBackend/1.0");

            // Construcción del JSON Schema 3
            String jsonPayload = buildPushPayloadJson(appId, provider, token, title, message);

            // Envío del cuerpo de la petición
            con.setDoOutput(true);
            try (DataOutputStream wr = new DataOutputStream(con.getOutputStream())) {
                wr.write(jsonPayload.getBytes("UTF-8"));
                wr.flush();
            }

            code = con.getResponseCode();

            // Lectura de la respuesta (InputStream para 2xx, ErrorStream para 4xx/5xx)
            InputStream is = (code >= 200 && code < 400) ? con.getInputStream() : con.getErrorStream();
            if (is != null) {
                try (BufferedReader in = new BufferedReader(new InputStreamReader(is, "UTF-8"))) {
                    String inputLine;
                    while ((inputLine = in.readLine()) != null) {
                        result.append(inputLine);
                    }
                }
            }

            WsLog.i(TAG, methodName + "-> response :[" + code + "] " + result.toString());
        } catch (IOException io) {
            WsLog.e(TAG, methodName + "-> ErrorIo :" + io.toString());
            return null;
        } catch (IllegalStateException is) {
            WsLog.e(TAG, methodName + "-> ErrorIs :" + is.toString());
            return null;
        }

        return new FCMResponse(code, result.toString());
    }

[shai-almog]

We deployed a server-side fix for the HTTP 406 problem. Your Accept: */* header is supported, changing it isn't required for this fix. Please try a fresh test request. Successful admission should return HTTP 202 with JSON containing deliveryIds and quota. Avoid retrying previous 406 requests automatically, since they may already have queued notifications.

We've also expanded the [Push Notifications guide](https://www.codenameone.com/developer-guide/push-notifications/) with step-by-step Console setup, credential examples, and classic-to-V3 migration instructions.

To clarify the points you raised:

• appId is the application UUID under Push → Overview → Server API → Copy ID. The Client binding key and mobile package/bundle name are separate values.
• iOS credentials require a JSON object wrapping the .p8 contents. Your structure is on the right track; the guide now includes the full example:

{
  "teamId": "YOUR_APPLE_TEAM_ID",
  "keyId": "YOUR_APNS_KEY_ID",
  "topic": "com.example.yourapp",
  "environment": "production",
  "privateKey": "-----BEGIN PRIVATE KEY-----\nYOUR_KEY_CONTENTS\n-----END PRIVATE KEY-----"
}

Use production for App Store/TestFlight installations and sandbox for development-signed installations. Include the complete .p8 text, with line breaks encoded as \n.

• Saved credentials remain blank intentionally. Check Configured in Settings or Ready under Overview’s Channel readiness for the same selected application. Those labels confirm a credential is stored; a test send verifies it works.

The Windows application-selector difficulty is a separate issue and wasn't changed by these fixes. Which browser and version are you using, and does the problem occur when opening the list, scrolling, or selecting an application?

[DurankGts]

curl -X POST https://cloud.codenameone.com/api/v3/push/messages
-H 'Authorization: Bearer YOUR_SERVER_API_KEY'
-H 'Content-Type: application/json'
-d '{
"appId": "APPLICATION_ID",
"targets": [
{"provider":"fcm", "token":"OPAQUE_DEVICE_TOKEN"},
{"provider":"apns", "token":"OPAQUE_DEVICE_TOKEN"}
],
"message": {
"schema":3,
"title":"Order shipped",
"body":"Order 4815 is on its way",
"data":{"orderId":"4815"}
}
}'

using this parameter to new v3 API push notification where can I set not visible data like option type 3 in legacy Api? in data?

[shai-almog]

It depends on which push API your installed apps use.

Apps still using PushCallback (no new mobile release): don't use data, because PushCallback never receives it. Use the classic payload with the same type and body you send today:

{
  "appId": "APPLICATION_ID",
  "targets": [{"provider": "fcm", "token": "DEVICE_TOKEN"}],
  "message": {
    "classic": {"type": 3, "body": "Visible text;hidden payload"}
  }
}

push() receives the hidden part just as before. Don't combine classic with title, body or data in the same message.

Apps updated to PushClient: yes, put the hidden values in data. They arrive in PushListener.onMessage() alongside the visible title/body. For a push with no visible notification, send it as a silent/data-only message.

[DurankGts]

It depends on which push API your installed apps use.

Apps still using PushCallback (no new mobile release): don't use data, because PushCallback never receives it. Use the classic payload with the same type and body you send today:

{
  "appId": "APPLICATION_ID",
  "targets": [{"provider": "fcm", "token": "DEVICE_TOKEN"}],
  "message": {
    "classic": {"type": 3, "body": "Visible text;hidden payload"}
  }
}

push() receives the hidden part just as before. Don't combine classic with title, body or data in the same message.

Apps updated to PushClient: yes, put the hidden values in data. They arrive in PushListener.onMessage() alongside the visible title/body. For a push with no visible notification, send it as a silent/data-only message.

ok some question are answered here. This means that I can continue sending message to legacy apps using the new push api but using this payload.

[DurankGts]

Hi again. I'm trying to implement the new push notification v3 in my app. I read all documentation. I registered My

push = PushClient.builder(cn1PushKey).listener(pl).build(); in init() method. I don't Know why the method pushId = com.codename1.push.Push.getPushKey(); it return the push token if I don't called this method yet?

private static void registerPushNotification() {
    if (push != null) {
        Log.i(TAG, "registerPushNotification()->registering...");
        push.register();
    }
}

I removed the PushCallBack from my main class

this method Push.getPushKey() it continue working with the new Implementation?

[shai-almog]

Yes, Push.getPushKey() still works with the standard Android/iOS push implementation when using V3. It reads the device token saved in preferences, so it can return a token from a previous run or an earlier version of your app, before you call push.register() this time. Removing PushCallback doesn’t clear that saved token.

PushClient.builder(cn1PushKey).listener(pl).build() only creates the client. You still need to call push.register() to activate it and request registration. Don’t skip that call because Push.getPushKey() already returns a value.

For new V3 code, use your listener’s registration callback:

@Override
public void onRegistration(PushSubscription subscription) {
    String token = subscription.getToken();
    String provider = subscription.getTransportId();
    // Update your backend if it stores device tokens.
}

These give you the token and provider for V3’s targets fields. The callback can run more than once, so replace any previously stored token when it does. A saved token alone doesn’t confirm that the current registration or notification permissions are valid.

[DurankGts]

this means that onRegistration() can run any time ?

onRegistration() runs after initial native registration and can run again when a provider rotates its token. Replace the previous server-side token for that installation.

[shai-almog]

Yes.

Once you call push.register(), treat onRegistration() as a callback that can run more than once, rather than only during initial setup.

It can run immediately with a previously saved token, again when native registration returns, and later when the provider reports a token change. Multiple calls can contain the same token, so a callback doesn’t necessarily mean it changed.

Each time, update or insert the token and provider for that installation in your backend. Repeating that update with the same values should be harmless.

The callback runs on the EDT.

[DurankGts]

other questions. If I migrated to new push server and I configure in the cn1 console the in android an ios side

Do I need to update all my apps to implemente PushClient to avoid update the push certificate every year in the ios case?

Do I need to create and app in your push console to every apps that i created using .p8 file and fcm in android? or this .p8 configured work to all my apps with out renew every year?

My published apps that use Legacy push notification it can receive push notification from the v3 of your push notification or I need to continue sending the old parameters to receive push messages?

[shai-almog]

You don’t need to update your published apps to PushClient just to stop renewing the iOS push certificate. The .p8 key authenticates the server to Apple. Your installed apps can keep using PushCallback.

Apple’s APNs signing keys don’t expire annually, although they can be revoked. This concerns push authentication only, app-signing certificates and provisioning profiles are separate. See Apple’s documentation.

Create one Console Push application for each logical app and environment. The Android and iOS versions of the same app can share that entry, with their respective credentials configured.

You can reuse an APNs .p8 key across apps in the same Apple team if its scope permits those apps and the required environment. Each Console application still needs its own configuration, with topic set to that app’s iOS bundle ID. Saving a key for one application doesn’t automatically configure your other applications. Apple supports both team-scoped and topic-specific keys. Key configuration.

For Android, configure the Firebase service-account credential for the Firebase project used by that installed app.

Your published legacy apps can receive notifications sent through the V3 endpoint. Send JSON to https://cloud.codenameone.com/api/v3/push/messages, using your server API key, the Console application UUID, and a message.classic payload:

{
   "appId": "APPLICATION_UUID",
   "targets": [
     {"provider": "apns", "token": "EXISTING_IOS_DEVICE_KEY"}
   ],
   "message": {
     "schema": 3,
     "classic": {
       "type": 1,
       "body": "Hello"
     }
   }
}

Keep the numeric type and body encoding your existing app expects. For Android, use provider fcm and its device key. Existing cn1-ios-, cn1-fcm-, and cn1-gcm- keys are accepted.

This route uses the credentials saved in the Console, so you don’t send cert, certPassword, or auth with each request. If you continue using /push/push, keep its existing form parameters; changing the hostname alone doesn’t switch those requests to your Console .p8 configuration.

The migration guide covers both paths. Test the V3 classic request against an existing installed app before switching production sends.

[DurankGts]

you need to fix this selector in Win11. It's very dificult to selected the second item because the wheel of the mouse increase so many. check the video

Issue.selecting.aplicacion.in.push.console.mp4

[DurankGts]

this is very important to fix. It's imposible to select the other application to copy de server Api

[shai-almog]

We'll look into it.