Level 3

AEM Push Notifications

Forum|Forum|9 years ago
June 30, 2016
4 replies
5588 views

Hello everyone

I'm currently trying to add the ability to send push notifications from AEM to a mobile application. For that, I have followed the documentation listed here: https://docs.adobe.com/docs/en/aem/6-2/develop/mobile-apps/apps/push-notifications.html. I've decided to go with Pushwoosh for the notifications. I have everything filled in correctly (atleast I presume so, but in AEM it tells me that the link is succesful), but whenever I try to launch the application in an emulator or actual device, the application crashes instantly.

I've build the application using the CLI and during the process there have not been any errors or whatsoever that indicate something is wrong.

If you've had something similar happening and found a resolution, please help me out here.

Kind regards

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

smacdonald2008

Level 10

I have asked the Eng team to take a look at this question.

D

dylanr46798176Author

Level 3

Well, I did manage to run the app before without the push notifications added to it, so I would seem logical to me that there is something wrong with it inside of my application which causes it to crash. I will try to get some kind of logging and see if that makes me any wiser. Also, I am trying to make it for Android only for now, with iOS added in the future.

mnew

Adobe Employee

Hi Dylanr,

It's tough to know what's going on based on your description, so I would start by asking whether you're on iOS or Android.

If iOS, you can run the app in Xcode and you should get some logging on the console.
If you're running Android, you can run "adb logcat | grep CONSOL" and then start the app in another shell; that should give you some good logging. If that doesn't give enough info, try it with just "adb logcat".

Let us know how that works for you. My feeling is if the app is not starting, it would not be because of the push notification stuff.

Mike New

kautuk_sahni

Community Manager

As mentioned by Michale,

If the app is on Android, you can get logging information by :-

Way 1:
Please download the free “aLogcat” application from the Google Play app store.

Steps:
1.Start intended app (Lets say: it is "AppName") on the device. – if it crashes, repeat this step 2-3 times
2.Immediately after, start "aLogCat app" and wait approximately ~1 minute
3.Press “Menu” button and select “Filter”
4.Type “AppName” in the text field and press “Okay” button
5.Wait approximately ~1 minute
6.Press “Menu” button and select “Share”
7. Collect log via any sharing option you have access (i.e: can send to your email, share via Blutooth etc)

Way2:
1. Download DroidExplorer from here: http://de.codeplex.com/ and Install in your PC
2. Connect your device via USB (I assume you have USB driver for that device installed) and turn ON developer options and allow USB debugging
3. Run DE in the PC, click on LogCat Console and see its running.
4. Now run the intended app
5. Reproduce the crash
6. Immediately, Save the logcat.

If app is on IOS:-

Link:- https://help.getpocket.com/customer/portal/articles/500338-how-to-find-the-iphone-ipad-app-crash-logs

Link:- https://www.raywenderlich.com/23704/demystifying-ios-application-crash-logs

I hope this helps.

Thanks and Regards

Kautuk Sahni

D

dylanr46798176Author

Level 3

This is what my logs tell me.

ActivityManager( 1083): Start proc com.adobe.cq.mobile.geometrixx.outdoorsapp for activity com.adobe.cq.mobile.geometrixx.outdoorsapp/.MainActivity: pid=19485 uid=10175 gids={50175, 9997, 3003, 1028, 1015} abi=armeabi-v7a
WindowStateAnimator( 1083): Starting window displayed
PhoneWindowManagerEx( 1083): Call!!!getLGSystemUiVisibility. =0x0
StatusBarManagerServiceEx( 1083): setLGSystemUiVisibility(0x0)
StatusBarManagerServiceEx( 1083): manageNaviBtnDisableList userId=0 what=0x0 pkg=WindowManager.LayoutParams
AndroidRuntime(19485): FATAL EXCEPTION: main
AndroidRuntime(19485): Process: com.adobe.cq.mobile.geometrixx.outdoorsapp, PID: 19485
AndroidRuntime(19485): java.lang.RuntimeException: Unable to get provider com.google.firebase.provider.FirebaseInitProvider: java.lang.IllegalStateException: Incorrect provider authority in manifest. Most likely due to a missing applicationId variable in application's build.gradle.
AndroidRuntime(19485):    at android.app.ActivityThread.installProvider(ActivityThread.java:5015)
AndroidRuntime(19485):
   at android.app.ActivityThread.installContentProviders(ActivityThread.java:4607)
AndroidRuntime(19485):    at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4547)
AndroidRuntime(19485):
at android.app.ActivityThread.access$1500(ActivityThread.java:148)
AndroidRuntime(19485):    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1344)
AndroidRuntime(19485):
at android.os.Handler.dispatchMessage(Handler.java:102)
AndroidRuntime(19485):    at android.os.Looper.loop(Looper.java:135)
AndroidRuntime(19485):
   at android.app.ActivityThread.main(ActivityThread.java:5272)
AndroidRuntime(19485):    at java.lang.reflect.Method.invoke(Native Method)
AndroidRuntime(19485):    at java.lang.reflect.Method.invoke(Method.java:372)
AndroidRuntime(19485):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:909)
AndroidRuntime(19485):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:704)
AndroidRuntime(19485): Caused by: java.lang.IllegalStateException: Incorrect provider authority in manifest. Most likely due to a missing applicationId variable in application's build.gradle.
AndroidRuntime(19485):    at com.google.firebase.provider.FirebaseInitProvider.zza(Unknown Source)
AndroidRuntime(19485):    at com.google.firebase.provider.FirebaseInitProvider.attachInfo(Unknown Source)
AndroidRuntime(19485):    at android.app.ActivityThread.installProvider(ActivityThread.java:5012)
AndroidRuntime(19485):    ... 11 more
ActivityManager( 1083): Force finishing activity com.adobe.cq.mobile.geometrixx.outdoorsapp/.MainActivity

After seeing this, I manually added an applicationId to the build.gradle file and the application now seems to run, however, push notifications don't seem to work quite yet. I made a connection with PushWoosh and tried sending a notification from my AEM instance (which is on localhost), but nothing really happened afterwards.

mnew

Adobe Employee

Not sure if you're still having this issue. I was out of the office, and didn't see the new posts...

If you sent a push and nothing happened, one thing you could do is log into your Pushwoosh account and see if it actually sent it. Pushwoosh records every push sent, so you will see it successful, failed, or you won't see it, and that will indicate whether the problem is on the server or the device, hopefully.

Mike

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded