Andrei,
I have verified things are working on Adobe's side. I followed the steps below. Note the different steps in the Google part - our online docs will be updated to reflect these changes, hopefully soon.
Let us know if you have any questions.
--------------------------------------
AppBuilder
Click Project Settings and hit the Create button to create a new project. Enter minimal data in fields.
Go to Content & Layouts and add an Article
Add the article to the "default" collection.
Go to Apps and Create an app for Android. Choose a unique Bundle ID and remember it.
While in this wizard, or before it, you need to create an app in Google Firebase; and you need this Bundle ID.
Google
- Log into Google Firebase (get an account if you don't have one) (https://console.firebase.google.com/ ).
- Create a project if you don't have one.
- Add an app to the project ("Get started by adding Firebase to your app"), on main project page.
- In Android package name enter your Bundle ID.
- Click Register App
- Download the config file (google-services.json) and save it.
- Click Next
- Ignore the next step called Add Firebase SDK
- You won't be able to run your app yet, so skip this step too.
- Click on the gear next to Project Overview. Choose "Project Settings"
Back in AppBuilder, on the Create New Android App screen, under the App Details tab, go to Android Push Notifications.
- Check Enable push notifications.
- Click on Upload and find your google-services.json file from earlier. It should show the package name from the project, and the project number and and an SDK App ID too.
- Click the Assets tab and upload a square asset. This one will be your app's icon on people's devices.
- If you need any plugins in your app, go to the Plug-ins tab and choose them.
- Click Submit when all done.
- Back on the Apps screen, the Downloads may show a busy image, which eventually becomes a link to the unsigned app.
- Click the link to download the app.
- Download the App Signing tool from the same page (the cloud icon with the down arrow on it). Install the tool on your computer (It's called "AEM Mobile Signing Tool").
Publish the Article
- Go to the Content & Layouts page and select the article you added. Click on Publish to publish it.
- (This step can even be done after Signing and Installing the App, below.)
Signing and Installing the App
- Create a cert for signing your app. This page describes how: https://helpx.adobe.com/digital-publishing-solution/help/android-publishing-guide.html
- Run the signing tool.
- In the tool, enter the .apk file you downloaded.
- Enter the name and path of the .p12 file you created earlier, and the password for it.
- Click on Sign Application. It should create another apk file next to your first one, but with "-signed" in its name.
- Get the apk to your device. You could just move it to Creative Cloud, One Drive, or Google Drive, and use the same app on your device to open it. Opening it should install the app.
- Open the app, go to Settings, and ensure "Allow push notifications" is checked.
Notifications
- In AppBuilder, go to the Notifications page.
- Click Push Credentials, and then click on the Android tab.
- Select the app and Click the + Add Credentials at the top of the page.
- For Server API Key, go back to your Google Firebase project settings. Click on Cloud Messaging, and copy the "Legacy server key". This is the Server API Key, so paste it into that field.
- For Project Number, add the Sender ID from the same page as your Server API Key.
- Click Create
- To send a notification, select Notifications, choose the Android tab, and click Create -> Text Notification. By default (if you do not change Delivery Options) it will send the notification as soon as you click Create. Fill out the Message field, and click Create.
- It should not matter if your app is running or not.
- You should normally receive the push notification soon, normally within a few seconds.
--------------------------------------------------
Michael, thank you very much for the detailed steps. I also noticed that documentation was recently updated:
However, I am still unable to get notifications to work. I tried it on our existing app, as well as creating a brand new project to test on, as you outlined above. I downloaded the latest Signing Tool and re-created the .p12 file to eliminate the possibility that I'm using outdated parts.
Every time I sent a notification on AEM Mobile dashboard, the history showed that Target Devices and Devices Sent were greater than 1, but I never received anything on my device. (Notifications were definitely enabled)
We'll have a call with an Adobe Technical Consultant soon to figure this out. I'll share an update once we get this resolved.
