Pushwoosh/pushwoosh-appcelerator-titanium

Android: latest version of the module doesn't work with 4.2.x and 4.1.x

Closed this issue · 6 comments

rborn commented

Hi,
It seems that I can't make any device with these versions of android register for push.
The only thing I can see in the logs is:

Could not find class 'android.app.AppOpsManager', referenced from method com.pushwoosh.internal.utils.e.b

Any idea?
Thank you.

Could not find class 'android.app.AppOpsManager', referenced from method com.pushwoosh.internal.utils.e.b

It should not affect device registration.

Do you get the registerForPushNotifications() callback invoked?
Could you also share full device logs?

rborn commented

No, the event doesn't trigger the callback :(

05-10 13:45:57.946: D/PushnotificationsModule(2634): (KrollRuntimeThread) [122,3685] initialize called
05-10 13:45:57.950: E/Pushwoosh(2634): Unrecognized log level: VERBOSE
05-10 13:45:57.950: I/Pushwoosh(2634): Log level: NOISE
05-10 13:45:57.950: V/Pushwoosh(2634): [RegistrationPrefs] Saving regId on app version 311
05-10 13:45:57.954: I/Pushwoosh(2634): HWID: ed555c0b4997533c
05-10 13:45:57.954: I/Pushwoosh(2634): [PushManager] App ID: E3A5A-B44BC
05-10 13:45:57.954: I/Pushwoosh(2634): [PushManager] Project ID: 122494198821
05-10 13:45:57.954: I/Pushwoosh(2634): [PushManager] This is android device
05-10 13:45:57.954: I/dalvikvm(2634): Could not find method android.os.PowerManager.isInteractive, referenced from method com.pushwoosh.module.NotificationFactory.isAppOnForeground
05-10 13:45:57.954: W/dalvikvm(2634): VFY: unable to resolve virtual method 1906: Landroid/os/PowerManager;.isInteractive ()Z
05-10 13:45:57.954: D/dalvikvm(2634): VFY: replacing opcode 0x6e at 0x0056
05-10 13:45:57.958: V/Pushwoosh(2634): [PushRegistrarGCM] number of receivers for info.rborn.mst: 5
05-10 13:45:57.958: V/Pushwoosh(2634): [PushRegistrarGCM] Found 1 receivers for action com.google.android.c2dm.intent.RECEIVE
05-10 13:45:57.958: W/TiAPI(2634):  ================================= pushHelper ================================================
05-10 13:45:57.958: W/TiAPI(2634):  Ti.Network.remoteNotificationsEnabled undefined
05-10 13:45:57.958: W/TiAPI(2634):  Ti.Network.remoteNotificationTypes undefined
05-10 13:45:57.958: W/TiAPI(2634):   
05-10 13:45:57.958: W/TiAPI(2634):  pushnotifications.getPushToken() 
05-10 13:45:57.958: W/TiAPI(2634):  persist.get("triedToRegisterForPush") undefined
05-10 13:45:57.958: W/TiAPI(2634):  isPushEnabled() false
05-10 13:45:57.958: W/TiAPI(2634):  isUnregistered() undefined
05-10 13:45:57.958: W/TiAPI(2634):  =================================================================================
05-10 13:45:57.958: W/ActivityManager(328): Unable to start service Intent { cmp=info.rborn.mst/com.pushwoosh.internal.utils.LockScreenService }: not found
05-10 13:45:57.978: D/Pushwoosh(2634): [RequestManager] Try To send: getInApps

05-10 13:45:58.194: I/Pushwoosh(2634): [RequestManager] 
05-10 13:45:58.194: I/Pushwoosh(2634): x
05-10 13:45:58.194: I/Pushwoosh(2634): |     Pushwoosh request:
05-10 13:45:58.194: I/Pushwoosh(2634): | Url: https://07353-706E1.api.pushwoosh.com/json/1.3/getInApps
05-10 13:45:58.194: I/Pushwoosh(2634): | Payload: {"request":{"v":"4.10.6","application":"E3A5A-B44BC","language":"en","hwid":"ed555c0b4997533c","device_type":3,"userId":"ed555c0b4997533c"}}
05-10 13:45:58.194: I/Pushwoosh(2634): | Response: {"status_code":200,"status_message":"OK","response":{"inApps":[]}}
05-10 13:45:58.194: I/Pushwoosh(2634): x
rborn commented

Hi any news on this?
You can test it with Genymotion and a simulator with 4.1.1 or 4.2.2 if you don't have a device.
Thank you.

PushwooshSample works on both Android 4.1 and Android 4.2.
As I see from your log, application didn't even try to register for push notifications. Are you 100% sure you call [registerForPushNotifications()(https://github.com/Pushwoosh/pushwoosh-appcelerator-titanium/tree/master/Documentation#registerforpushnotifications) method?

rborn commented

Hi, the same app works fine for android 4.4.4+

rborn commented

@DimanAM I found the issue - getNotificationSettings returns{"enabled":false} for these android versions.
I use this to avoid registering when the user disabled in the phone Settings.