Now that I see the sample (android) application is registered for Bluemix-PUSH notifications.I have configured the Bluemix Application's info (APP ROUTE, APP UID)
I am using a Bluemix app from ----https://github.com/ibm-bluemix-mobile-services/bms-samples-android-hellopush. I have pulled this project, and built it with the proper dependency gradle settings.
But the problem is that I can not see the Push message sent from the Bluemix app on the emulator's push-registered Android App. Also I could not see an error in log files.
Are there any other ports that need to be opened on Secured bank Network in order to receive pushes from Bluemix?
I am using Android Studio 1.5.1, JDK 1.7 and Emulator - API 19 (With Google API enabled).
I built the sample application using Android API 23.0
What should we check on PUSH notifications on studio's emulator?
If there are no errors anywhere, chances are that your Google app credentials have been configured using the incorrect API key.
Ensure that you have created a Server Key and not an Android Key
Related
I have deployed my Bot Framework v4 app as a Web App Bot to Azure. I can connect to it in Web Chat in the Azure Portal, but it is crashing when I message it via Twilio.
I am attempting to debug this, but when I try to attach via Visual Studio's Cloud Explorer I get the error in the screenshot. I have also tried attaching directly by using the username and password in my publish profile, but that always results in the breakpoints saying the symbols haven't been loaded once it is connected. When I look at the debug modules, I don't see any pertaining to my bot's dll. This is with the publish profile set to the Debug configuration, so no issue with optimized code.
Any suggestions are greatly appreciated!
I have seen this error during one of my attempts. I ended up removing the current version of code from the web app by using the Kudu Console, restarting the app service and then publish again from VS using the publish profile.
Was able to make some progress on debugging by attaching to SITENAME.scm.azurewebsites.net instead of SITENAME.azurewebsites.net.
Doesn't explain why Cloud Explorer still can't connect, but at least unblocks me for now
I'm getting the following error when I try to access the App Service node in the Server Explorer after connecting to my Azure Subscription.
Here's the complete Error Message.
---------------------------
Server Explorer
---------------------------
Unable to retrieve Web Apps from some subscriptions:
Subscription Visual Studio Premium with MSDN: The resource type 'apiapps'
could not be found in the namespace 'Microsoft.AppService' for api version
'2015-03-01-preview'. The supported api-versions are '2015-03-01-alpha'.
---------------------------
OK
---------------------------
I am able to access other nodes, just not the App Service node wherein I have 2 Apps installed and running. 1 is a Web App, the other is an Api App that I originally published as a ASP.Net Core API App.
Due to this, I'm having to FTP into the Site and browse through log files and download them to view them. Very time consuming and distressing.
Even after I deleted the ASP.Net Core API app I am still not able to access this node from within Visual Studio 2015.
I have a question, I created recently an API app using visual studio 2017, I noticed that the name of the app says it's "API app host" which is different from the earlier one created a year ago "API app".
the problem that I am facing is that while I am trying to publish using visual studio 2017, the application that has "API host app" isn't listed at all as a candidate in the list.
as a workaround I am downloading the publish profile from azure portal and using that to publish using visual studio, as the last one can't find the targeted API app in the list.
is this a known issue ?
this picture shows that we have two types of API apps, API App and API app host
Make sure you have the Azure SDK 2.5.1 Release installed on your VS, you should be able to see something similar to the image below, this is how you can publish to App Api.
is there a way to debug azure app service (after migrating from azure mobile services) with node.js backend locally on MAC. i heard that one of the benefits for migration is the ability to debug locally. I looked in the documentation there's no clear tutorial on how to achieve that (specially there's a connection to the sql database that is maps the tables to the api calls.
i found the link below but i got confused how it will handle database sql server connections etc..
build and deploy a node.js api app
According to the article Advanced Debugging of the wiki for Node.js Tools for Visual Studio (NTVS), you can remote debugging of Node.js processes hosted on Windows Azure via Visual Studio with NTVS.
Althought Visual Studio has been not supported on MAC by now, you can try to use Visual Studio Online service to debug, please see the video Debugging node.js on Channel 9.
Any concern, please feel free to let me know.
I have a Windows 8 app in the store that uses Azure Mobile Services to send push notifications. I'm working on a Windows Phone 8 version of the app now but I can't seem to get the Mobile service to push notifications to both platforms. This page suggests that it's possible.
When sending a push to Windows Phone I get this error "The cloud service is not authorized to send a notification to this URI even though they are authenticated."
If I remove the Package SID from the push settings of the Mobile service then pushing to Phone works but to the Windows 8 app doesn't.
Is this a scenario that's supported? Is there any sample demonstrating it?
thanks!
I am able to send notifications to both a Windows Store and WP8 apps that use the same backend Mobile Service. Can you share the code that you are using to send out the notifications to both platforms? The error message you are getting looks like the error message from the Windows Notification Service (http://msdn.microsoft.com/en-us/library/windows/apps/hh465435.aspx - see the Response Codes section), not the Microsoft Push (Phone) Notification Service.
Also, make sure that you have associated your app with the Store. Someone posted in the Azure Mobile Services forum with the same error message and this was the cause. http://social.msdn.microsoft.com/Forums/windowsazure/en-US/05b0ea71-f498-46bc-b6c0-16491b14ea99/error-in-push-notifications?forum=azuremobile
Note that the Package SID and Client Secret that you specify in the Azure portal (on the Push tab) only apply to Windows Store apps - Mobile Services does not currently support authenticated notifications for WP8.