Seems like the Bluemix Push Notification service has been subject to changes recently. Indeed, when you click on the Mobile Options button in the configuration panel, a message in the pop up window states that The use of App Route parameter is deprecated.
However, this app route parameter was required when intializing the BMSClient plugin (BMSClient.initialize(BLUEMIX_PUSH_APP_ROUTE, BLUEMIX_PUSH_APP_GUID))
What is the right way to initialize the ibm-mfp-push plugin now that the app route parameter is deprecated?
I know that the ibm-mfp-mush cordova plugin is currently being updated. Will the update address that issue? Is there a status about the release of the updated version of the plugin?
Thanks
So for the time being, continue to use your regular app route (from the MobileFirstServices starter or other).
The new ibm-mfp-push (probably will be renamed bms-push) will address this issue. It is currently in the backlog. The estimated time of completion is about one month from now.
Related
When trying to access https://console.actions.google.com/project/*project-id*/release/ I get following error message:
If I open the developer console in Chrome and check for failed network calls it shows a 504 on https://console.actions.google.com/m/actions/agents/versions/get?projectNumber=*project-number* with this body:
I tried clearing my cache and tested on multiple browsers but since it also happens on other devices I guess this is a server issue.
Anyone who can help me out?
I was experiencing the same issue for a published Action.
According to Actions on Google support, it's because the cumulative size of all the versions of our action were causing that version request to timeout when it tries to pre-load them all at once.
The solution for me was to, raise a support request (I clicked the link in your screenshot, Actions on Google Support, included a screenshot of that message, request type deployment issue and a brief description of not being able to access the deploy/test tabs) and then when support responded, they asked which versions to keep/delete. I said delete all except one version either side of the currently deployed version.
A note on preventing this - I couldn't find a consistent method for deleting versions/releases. I believe the versions created in Dialogflow by doing a Publish A Version can be deleted in Dialogflow. But versions created by releases in Actions on Google, have the delete options greyed out in Dialogflow, and I couldn't find where to do that in Actions on Google.
I deployed the production release for my first Google Action. But even 2 weeks after the approved deployment I can find my action neither in the Google Assistant store nor directly via voice activation.
The test versions ran fine and was found every single time. So the invocation name should not be the problem. When I use the generated action link from the console I find the action in the store and can send it to my Smartphone, where I can start it with the sent link. But after closing the app I cannot open it again via voice.
I used two different google accounts on different devices (all are set up in the right language: german), but no chance.
Is this a mistake on Googles side or do I miss anything? In this state I have to open the action every time over the action link which is useless for a voice app :)
Here is the link to my action: https://assistant.google.com/services/invoke/uid/000000c77f740137?hl=de
The invocation would be for example: "Mit Erfolgs-Fans sprechen" (like said, on the test this name was found every single time)
This happened to me too. Though it wasn't in production when I faced it. I was also not able to see the action in Assistant-enabled devices (Google home app/assistant).
It is probably not the invocation name issue, it is just that the action is not being made visible across all the platforms. Some of the solutions I tried were-
Clean cache of the device
Create a new action with everything just the same as in your current actions. It worked once for me!
Go to GCP and under your project, try to understand if there is any pending activity.
Once I created so many actions because I wasn't able to see it that after around 30 days all those actions started to become visible. So, if you can wait that is fine.
In the end, do contact their support with all the relevant information. I hope they should be able to help.
Thank you!
I'm having a problem after adding the AWS Amplify iOS SDK REST API to my project. I am unable to build my project due to 3 fatal compiler errors in one Amplify added file (*Client.swift under the generated-src folder), and I don't know what to do about them.
Everything was going very well with my iOS app after leveraging the Drop-in UI for authentication: I was able to sign in via my pre-existing Amazon Cognito User Pool. So, things were working.
Next step, I wanted to access a pre-existing DynamoDB table. It seems that the way to do this in an Amplify context is to add the REST API.
Following the steps in the link above, I knew Amplify was doing something I didn't want it to do by creating its own Cognito User Pool; I guess because I specified that I wanted to "Restrict API access" to authenticated users. What I expected is that I would restrict access on the basis of my already existing Cognito User Pool, not a new one.
Anyway, that is not my immediate problem.
After issuing the pod install --repo-update command, I added the new generated-src folder to my project. I thought it was curious that my awsconfiguration.json had not changed. At that point, as instructed, I attempted to build the project but was unable to do so due to those 3 errors.
/Users/xxxxx/Dev/iOS/xxxxxxxxxx/generated-src/xxxxxxxxxxxClient.swift:148:34:
Cannot assign to property: 'endpoint' is a get-only property
/Users/xxxxx/Dev/iOS/xxxxxxxxxx/generated-src/xxxxxxxxxxxClient.swift:174:13:
Value of type 'xxxxxxxxxxxClient' has no member 'invokeHTTPRequest'
/Users/xxxxx/Dev/iOS/xxxxxxxxxxx/generated-src/xxxxxxxxxxxClient.swift:195:13:
Value of type 'xxxxxxxxxxxClient' has no member 'invokeHTTPRequest'
I cannot advance to the next step (thinking it might be the reason for those errors) because the Build Settings tab for my project doesn't show an Objective-C Bridging Header category. (Yes, I presume? Until built?)
Can someone help me out?
The good developers over at AWS Amplify's iOS SDK Github repo answered my question. As a result, they are updating the REST API guide to reflect the proper order of steps.
To summarize: you must add the Objective-C bridging header path to the Build Settings for the project. It was not obvious to me where to find this setting, but they posted a screenshot showing how to find it. Filtering without choosing those explicit settings did not turn it up in my case.
We have faced this type of problem.We are Developing phonegap app.We don't changed any code.But unfortunately my eclipse stop.And then we changed project location.then we open html page in browser.We got error like this
Please guide to us.
You can test your app inside a web server, that solved my problem, or you can simply delete "history.replaceState()" in your jquery.mobile.js file, if you don't use the browser history in your mobile app
Waiting for chrome developers to fix this issue from the last update.
I have an existing integration with Paypal using the java sdk. We're planning a production release, but we can't let it got to prod with the current log level of the sdk. It seems to be set to DEBUG and logs every request going/coming from Paypal. I guess there must be a parameter to add to the paypal_sdk_config.properties file, but I can't seem to guess it and documentation is inexistant on the matter.
Anyone has ever done this before?
We just discovered, going through the code source of the com.paypal.core.LoggingManager class, that the logger creation is not intuitive.
The logger name is always something like class for example: class com.paypal.core.APIService
It means that you cannot set the log level through this call
getLogger("com.paypal.core.APIService").setLevel(Level.WARNING);
To set the log level, you need to do that:
getLogger("class com.paypal.core.APIService").setLevel(Level.WARNING);
I just open an issue on the Paypal github repo for that strange behavior: https://github.com/paypal/sdk-core-java/issues/13