It would be nice to know in the CUSTOM ERROR MESSAGES section of the Error handling guide which calls actually work with custom error messages and shows it. As an example, as of right now, returning a soapFault in the getMediaMetadata shows An error occurred while adding songs to the Queue (701) instead of showing the custom error message.
I tested those calls with the desktop Sonos app for Mac and the Android app.
Showing it: getMediaURI, getMetadata, getDeviceAuthToken
Not showing it: getMediaMetadata, getAppLink
Can getMediaMetadata work with custom error messages too?
Related
I've setup react-native-twitter-signin package as like in documentation and works perfectly on Android. But I'm getting this error on iOS.
Possible Unhandled Promise Rejection (id: 1): Error: Twitter signin error.
Is it due to callback issue?
The problem for me was the I didn't put twitterkit-CONSUMER_KEY:// in the Twitter developer site.
Go to https://developer.twitter.com/en/apps/
Pick you app then press edit button on right side
Edit the details, and scroll to Callback URLs
Add twitterkit- (delete this and put your CONSUMER_KEY instead). It should look something like this:
twitterkit-23232123ddskdj231jhds
When using the delegate method crashlyticsDidDetectReportForLastExecution without the handler, crash reports are not being sent.
From the docs, this method "does not give you the ability to prevent the report from being submitted". However, that's not the case.
The delegate method is being called though. I'm using it to send logs to a custom server. But if implementing Crashlytics delegate, its report is not sent and does not appear on Fabric's dashboard.
I'm using Fabric 1.7.6 and Crashlytics 3.10.1.
When my service worker invokes a secured API that returns content, I do receive an error message, such that The Site has been updated in background. Can anyone please help me out ?
Based from this link, the message This site has been updated in the background is a forced message from the Chrome browser when the SDK cannot fetch the notification contents to retrieve. Notification contents are not sent to our background worker; instead we receive a signal to display a notification and then we fetch the notification contents from our server.
This behavior is most likely triggered by the user having multiple notifications pings, but only one message to receive.
You may also check this related SO post: Chrome Push Notification: This site has been updated in the background
Generally as soon as you receive a push message from GCM (Google Cloud Messaging) you have to show a push notification in the browser. This is mentioned on the 3rd point in here:
https://developers.google.com/web/updates/2015/03/push-notificatons-on-the-open-web#what-are-the-limitations-of-push-messaging-in-chrome-42
So it might happen that somehow you are skipping the push notification though you got a push message from GCM and you are getting a push notification with some default message like "This site has been updated in the background".
Hope this helps!
I am trying yodlee api on android but getting file not found exception when I called HTTP GET request on : Request URL=https://developer.api.yodlee.com/ysl/restserver/v1/providers?name=icici.
When I used java sample api as standalone java application it's work fine but in android it is giving exception. cobrand as well member login works fine on android.
You should first check the code, as this is not something which Yodlee API returns. Seems to be an issue with your android code. Do you mind updating the question with your code and actual exception you are getting?
I have made simple application using Ionic and cordova. Added Mobilefirst plugin in it. Also I have used security adapters in it ResourceAdapter and UserLogin Adapter which is provided by IBM.
Now I want to include push notification part in this project. So I have added push notificationMFP plugin in same project. Sender id and key in push settings. Added scope push.mobileclient also.
When I tried to call MFPPush.registerDevice javascript method I am getting failed to register device.
Failed to register device:"com.ibm.mobilefirstplatform.clientsdk.android.push.api.MFPPushException: Response: Status=404, Text: Error 404: SRVE0295E: Error reported: 404\n, Error Message: Not Found"
Also when App get initialized I can see in MFP console that particular device in devices list and when I login I can see user ID also get added in device information. So what is problem is something I am missing? Why device is not able to register for push?
The original issue in the question was resolved:
Yes. Now its working Its initialization issue. Just got it. Thnks.
The user then added a new issue via comments:
One more help I need. I am trying to send notification to particular User ID through MFP console. But device can not get any notification. But i cn see User ID against device id. So there is option to send to user id in console. But its not working for me
Unless you got an error in the console, this means that the notification in all likelyhood left the MobileFirst Server. From there there are numerous options why the sending will fail. See the Push Notifications Troubleshooting section.