I've recently ejected expo application into the bare workflow and changed the package name. Now I can't send notifications from my own backend using expo-server-sdk or expo notifications push tool. Error I get is the following:
[
{
id: 'e17a1f3a-7c5b-41fe-8446-89ba6cb22027',
status: 'error',
message: "Unable to retrieve the FCM server key for the recipient's app. Make sure you have provided a server key as directed by the Expo FCM documentation.",
details: { error: 'InvalidCredentials', fault: 'developer' }
}
]
{
'e17a1f3a-7c5b-41fe-8446-89ba6cb22027': {
status: 'error',
message: "Unable to retrieve the FCM server key for the recipient's app. Make sure you have provided a server key as directed by the Expo FCM documentation.",
details: {
fault: 'developer',
error: 'InvalidCredentials',
sentAt: 1597911004
},
__debug: {}
}
}
I've tested with android. After old server key failed I tried creating new server key and uploading it to expo server
expo push:android:upload --api-key
Which resulted in the same error. I tried deleting the api key from expo server (expo push:android:clear) first and uploading it again, same result. Then I tried to create a new firebase project and redoing the steps as described in expo documentation only to get same results. I even waited couple of days to see if problem will resolve itself while trying to come up with ideas. My knowledge and googling have failed me so any help would be greatly appreciated. If you need further information please let me know.
Thank you in advance!
Related
I'm trying to setup Push Notifications Setup and I have followed this documentation for the frontend and backend as well https://docs.expo.dev/push-notifications/overview/.
I have created FCM for android and I have used the API server key in the google-service.json that firebase gave it to me to put it in the project.
When I created the apk(to test the notification) in my logs it showed me this error:
[
{
id: 'c4b19090-cc75-482e-b194-a37647fd2af7',
status: 'error',
message: "There was an unknown error with the FCM server. See this error's details for more information.",
messageEnum: null,
messageParamValues: null,
details: {
error: 'ProviderError',
errorCodeEnum: 1,
fault: 'fcm',
fcm: [Object]
}
}
]
How can I solve this error?
I'm new to flutter, Unable to get the token from Huawei push notification in flutter.
I'm using below code to get data:
await Push.getToken("");
await initTokenStream();
Unable to get the token from huawei push notification in flutter. Getting error in push notification token with error code 907135003
Log
E/HMSSDK_HmsInstanceId( 5742): TokenTask failed, ErrorCode: 907135003 D/HMSLogger( 5742): singleEventMap -> {apiName=getToken, package=com.bghuawei.app, cpAppVersion=1.0.0, version=5.3.0.304, platform=Flutter, result=907135003, costTime=218, service=Cross-Platform, kit=Push, appid=105282649, model=OP4F2F, networkType=WIFI, callTime=1641433679625} I/HMSSDK_BaseHmsClient( 5742): Enter disconnect, Connection Status: 5
Can any one help me !! Thanks
Please refer to the URLs below for the error code description and solution. Please try to use the latest version of HMS Core per Shirley's comment above as well.
https://developer.huawei.com/consumer/en/doc/development/HMSCore-References/error-code-0000001050255690
https://developer.huawei.com/consumer/en/doc/development/HMSCore-Guides/error-code-0000001050994177
error code 907135003
This error is reported when the HMS Core version is too early and needs to be upgraded. Therefore, pls try to upgrade the HMS Core apk to the latest version.
I followed this doc to upload my assetlinks.json file to server, and it can be browsed by url like https://host/.well-known/assetlinks.json. However when I tested it using this tool and got an error "No app deep linking permission found for xxx at xxx" with json response as:
{
"maxAge": "599.999999805s",
"debugString": "********************* ERRORS \n Error: unavailable: Error fetching statements from https://host./.well-known/assetlinks.json (which is equivalent to 'https://host/.well-known/assetlinks.json'): URL_ERROR/3 [14] while fetching Web statements from https://host./.well-known/assetlinks.json (which is equivalent to 'https://host/.well-known/assetlinks.json') using download from the web (ID 1).\n* INFO MESSAGES ********************\n Info: No statements were found that match your query\n",
"errorCode": [
"ERROR_CODE_FETCH_ERROR"
]
}
Is there any solution for this issue? Thanks for any idea!
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?
I modified Q-municate powered by QuickBlox (which is open source) GitHub code and I put my own credentials to Firebase authentication but I am getting this error. I put all credentials, but still, I do not know what the error is.
I put all these credentials but it's still giving an error and also mentioned in the image about the error.
Project ID:
APP ID:
Package name:
These things I put in the project. Can anybody tell what the error mentioned in image is?
In current version of Q-municate (2.5) you need just add new parameter devFirebaseAuthProjectId=\"xxxxxxxxxxxxxxx\" to file q-municate-android/Q-municate_app/gradle.properties. Value for this parameter you can get in Firebase Developer Console, see screenshot: Additionally check SHA1 for your debug key in Firebase Developer Console.