Pushwoosh SDK Notification Issue - android

I have integrated the Pushwoosh SDK in my Android Application and it is working fine.
I have done the Cross Platform Setting to run the Android Application on my Blackberry Z10 device, the application is running finely but I am not able to receive the Notification on my Blackberry Z10 device as Android.
I am getting this error:
06-06 14:34:21.314: I/QNXNavigatorClient(8708260): Already active: com.packagename.pushdemo
06-06 14:34:21.662: I/QNXNavigatorClient(8708260): PackagesOpenedRunnable: [com.packagename.pushdemo]
06-06 14:34:21.662: I/QNXNavigatorClient(8708260): Shell com.packagename.pushdemo cannot join group, group was already joined
06-06 14:34:21.668: I/ActivityManager(8708260): Displayed com.packagename.pushdemo/.MainActivity: +347ms
06-06 14:34:24.118: E/QNXShrimpClient(8708260): com.google.android.c2dm.intent.REGISTER error(10108) = ""
06-06 14:34:24.124: W/ContextImpl(8708260): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendOrderedBroadcast:1061 com.android.server.QNXShrimpClient.onRegisterComplete:162 com.qnx.service.pps.shrimp.ShrimpController.onMessageReceived:128 com.qnx.service.pps.PPSObject.processMessage:292
com.qnx.service.pps.PPSObject.access$500:11
I am not able to get the Push Notification on my Blackberry Z10 device.

Have you set everything up correctly as in the following guide?
http://www.pushwoosh.com/programming-push-notification/blackberry/blackberry-10/blackberryandroid-runtime/
From what I see your app fails to register with BlackBerry. Make sure you have entered the correct appid and ppgurl in step 4 (android.cfg file).
If you are using BB push trial account the ppgurl should be as in the guide:
http://pushapi.eval.blackberry.com

Related

Expo notifications can't call `getExpoPushTokenAsync()`

Am currently trying to setup notifications on my managed expo project
Expo version 47.0.0
Expo notifications version 0.17.0
Device: Samsung Galaxy s10
Android version 12
I am currently just trying to get the basic setup itself working and retrieve my devices push token. This should be done using Notifications.getExpoPushTokenAsync() as described here.
The Problem
My error is strange, when I call getExpoPushTokenAsync it does indeed get me the expo push token, however shortly after my app crashes with the following messages
ERROR TypeError: undefined is not an object (evaluating '_$$_REQUIRE(_dependencyMap[1], "../../../src/util").types.isPromise')
WARN [expo-notifications] Error encountered while updating server registration with latest device push token. [TypeError: undefined is not an object (evaluating '_$$_REQUIRE(_dependencyMap[5], "#ide/backoff").computeNextBackoffInterval')]
I have tried
re-installing node_modules and expo-notifications but still get the same.
I can definitely see the #ide/backoff package is installed in my node_modules.
I also followed these instructions to setup firebase in app, even though my understanding is that it should work out of the box in expo go app while devving.
One other interesting thing is that I can call Notifications.getDevicePushTokenAsync() fine with no error. But still get the same error if i pass that in to getExpoPushTokenAsync method after. At a surface level it seems like somehow the request out to expo services to get the expo push token is both passing and failing 🤷‍♂️
const devicePushTokenResponse = await Notifications.getDevicePushTokenAsync();
const expoPushTokenResponse = await Notifications.getExpoPushTokenAsync({
devicePushToken: devicePushTokenResponse,
}); // <--- Returns token & errors a few seconds later
Couldn't see any other posts with this error and expo-notifications, so would be keen to see if anyone else has ran into / fixed a similar issue recently
Cheers
Alright I figured it out, it was somewhat hinted at by this line
ERROR TypeError: undefined is not an object (evaluating '_$$_REQUIRE(_dependencyMap[1], "../../../src/util").types.isPromise')
And more specifically the fact that a node_modules dependency is referencing 3 levels up in the file system.
The solution
Turns out that for some reason my module resolver (defined in babel.config.js) was resolving my project's util folder instead of the packages util folder. I think this was compounded by my metro config making use of the inlineRequires functionality to improve performance (see more)
I am sure there is some actual config that could be updated to exclude node_modules from using inline requires (i did try use a blocklist to no avail), but as an interim, i was able to get it working fine by changing the path of my util folder to be #my-project/util so that it avoids future collisions.
Hope this helps anyone who runs into the same issue in the future :)

MobileFirst 8.0 Direct Update not work and the app keep loading

Good day,
I upload a web resource archive to MobileFirst Console, I expected my mobile device will receive the direct update notification.
However, my app just keep loading.
I go check the mfp trace.log, it just keep printing
[3/9/20 19:52:01:788 MYT] 000000c1 id= com.worklight.common.util.JNDIUtils 1 JNDI Access (global scope) not found in cache for key mfp.cloud.devicelimit
[3/9/20 19:52:01:789 MYT] 000000c1 id= com.worklight.common.util.JNDIUtils 1 globalScopeLookup JNDI Access via globalScopeLookup to mfp.cloud.devicelimit => null
I try to google on this error message but didnt get any good result.
I run the following command to generate the web resource file:
mfpdev app webupdate --build
And then I upload it to MFP Console.
My cordova-plugin-mfp version is as follow:
"cordova-plugin-mfp": "^8.0.2020012903"
Its Cordova app.
There is no client side log, the console just log nothing until it hit timeout, then it only log timeout message.
Any Ideas?

WL.Client.connect() failed intermittently

I have an android application, when I deploy it to my Samsung Galaxy Note 4, and run the apps, the first time it run, it works fine. However, if I exit out the app and activate it again, it failed to connect to the server. After several attempt to try it again, occasionally it will work again.
Here is the code that resides in wlCommonInit:
WL.Client.connect(
{
onSuccess:connectivityCheckSuccess,
onFailure:connectivityCheckFailure,
timeout:5000
});
When it failed it will execute "connectivityCheckFailure" callback function
Here is the log showing in logcat:
01-12 11:49:31.099: D/NONE(17766): Request [/apps/services/api/Macros/android/init]
01-12 11:49:31.309: D/GCMClientFactory(17766): GCMClientFactory.useGooglePlayServices in GCMClientFactory.java:42 :: Google Play Services is not used because the play services library is not found. So using the default GCM helper implementation.
01-12 11:49:31.319: D/GCMIntentService(17766): GCMIntentService.doWakefulWork in GCMIntentService.java:152 :: GCMIntentService : Received a registration message from the GCM server
01-12 11:49:31.319: D/GCMIntentService(17766): GCMIntentService.onUnregistered in GCMIntentService.java:186 :: GCMIntentService: Unregistered at the GCM server
01-12 11:49:36.129: E/NONE(17766): Request timeout for [/apps/services/api/Macros/android/init]
Which shows the init is timing out.
Can anybody give me an idea what is wrong?

Modules do not start in Google App Engine Python on Development Server

Problem:
I am trying to create a simple app to try Modules in Google App Engine Python on Development Server(Development SDK 1.9.2). But I do not see the modules getting started at runtime(log messages specifying the ports on which they are started).
Logs when I start the app using the Launcher on the development server:
2014-04-13 02:40:47 Running command: "['C:\\Python27\\pythonw.exe', 'C:\\Program Files (x86)\\Google\\google_appengine\\dev_appserver.py', '--skip_sdk_update_check=yes', '--port=11080', '--admin_port=8003', u'C:\\gaurav\\coding\\python\\androidbackend1']"
INFO 2014-04-13 02:40:50,572 devappserver2.py:764] Skipping SDK update check.
INFO 2014-04-13 02:40:50,627 api_server.py:171] Starting API server at: http://localhost:59432
INFO 2014-04-13 02:40:50,631 dispatcher.py:182] Starting module "default" running at: http://localhost:11080
INFO 2014-04-13 02:40:50,634 admin_server.py:117] Starting admin server at: http://localhost:8003
INFO 2014-04-13 02:40:56,062 module.py:627] default: "GET / HTTP/1.1" 200 12
This Modules doc page at GAE for Python does not mention anything about development server. From another link, I figured out that on development server, all the modules are started at the beginning of app execution and they only differ in the port number of their URLs
Context:
I created a new app using the Google Launcher which generates a default "main.py" and "app.yaml". I then copied the "main.py" into a file named "modulem1.py", while retaining "main.py". I copied "app.yaml" into a file named "modulem1.yaml", while retaining the "app.yaml" file. I added the following line to "modulem1.yaml":
module: modulem1
I want to use Google Endpoints API to interact between the web app and Android app. So I need to use module for that and therefore I am trying a small web app with modules
I should be missing something obvious. Appreciate any help
If you are using the Google App Engine Launcher, then you will need to provide the full path to your second yaml file modulem1.yaml
Then once you start it, you can view the Logs and see that the modulem1 module has been launched at http://localhost:8080 and the default module has been launched at http://localhost:8081

Titanium android : unable to get the device token using com.activate.gcm module

I am unable to get the device token in the success method of gcm.registerC2dm instead i am getting null or '' value of device token please help me regarding this if some one has idea.
I am using pushnotifications module : com.activate.gcm version 0.5 android sdk : 2.3.3 titanium sdk : 3.00 GA
Regards:Ali

Categories

Resources