Parse.com Push Notifications on Windows 10 - windows-10-universal

I am already using Parse Notification on WP 8.1 its working fine but now I want to build new version of windows 10 but parse push notification not working so please if anyone using parse push notification on window 10 help me ?

There is a pending pull request for Parse Windows 10 support.
https://github.com/ParsePlatform/Parse-SDK-dotNET/pull/91
I'm using it currently and it's working.

Related

ReactJS web push notification at a certain time?

I'm trying to build a web application based on React.JS (not React-Native) and Django for its backend. I'm struggling right now on how to send push notifications on a specific time. Are there any useful modules/APIs that can support time based push notifications?
To be exact... even if I exit the website, as long as my browser (ex: Chrome) is on, I want to still be able to get a notification at the time I set.
Firstly the Front end framework is not much relevant , secondly you could use firebase push notification , generate a client side token for that browser and send it to your DB and store it, then you can use something like django-cronjobs and time it when you want a push say at 5 pm UTC on every day , set it there and in that you can use fcm to push notification to it.
Ref this github repo for fcm django you just need to put django-cronjob code to trigger that file.

How to make a call from web browser to phone using nexmo api?

I have made a dialer in salesforce and now I want to make a call from dialer to phone number
You can follow along this tutorial to get started: https://www.nexmo.com/blog/2018/08/21/phone-call-web-browser-nexmo-in-app-voice-vue-js-dr/

AWS IoT Subdomain Too Long for AWS IoT Button (Gen 1)

I'm trying to connect a generation 1 AWS IoT Button (the blue kind) to my AWS IoT core instance.
In the configuration, it says to input a subdomain that is 14 characters long so that it can create the endpoint for the button. However, my IoT endpoint is 18 characters long - it has an additional -ats at the end of it.
So, while my endpoint is actually
XXXXXXXXXXXXXX-ats.iot.us-west-2.amazonaws.com
It won't let me add the -ats at the end of it. So I'm stuck with
XXXXXXXXXXXXXX.iot.us-west-2.amazonaws.com.
Is there a way to input the full AWS IoT endpoint? Or is the -ats ending not needed and it's another issue with connecting the button to a network?
I had a similar problem trying to manually setup the AWS button.
As an alternative to using the tutorial to configure the button manually, I used the AWS IoT Button Dev application on an iphone. Using the iPhone app worked.
Apple App Store
Google Play Store
The resulting url in the console still contained the -ats suffix in the endpoint. I do not know if the app is bypassing the 14 character limitation, or if it is not needed, but this at least got me up and running with the button. If that is your goal, this should get you going.
You can also edit the html on the form in the developer console. The maxlength on the input element named "subdomain" is set to 14. Change that to >=18 and you should be able to submit the form.

PhoneProductId in appxmanifest: Upgrade from Silverlight to Runtime vs. Map Service Application Id (wp RT 8.1)

I'm updating an app from Windows Phone Silverlight 8.1 to WP Runtime 8.1 and got an issue with the "PhoneProductId" in the Package.appxmanifest:
1) Either I provide the Id from the old Silverlight version of the app. Then I can update it in the console via "AppDeployCmd.exe" /targetdevice:de /update MyApp_1.2.3.4_AnyCPU.appxbundle" with no user data being lost. But when I run MapRouteFinder.GetDrivingRouteAsync(...) I get an InvalidCredentials-error, since I haven't provided the proper Map Service Application Id, which in RT needs to replace the PhoneProductId (in Silverlight, it needed to be provided via c#, alongside the Authentication Token).
2) Or I provide the Map Service Application Id and can use MapRouteFinder.GetDrivingRouteAsync properly. But then I can neither /update the app (error message "Application is not installed" in the console) because of different PhoneProductIds in the two app versions. I also can't /install it without first uninstalling it ("Could not register package").
Anybody got a way out of this dilemma?
I've now uploaded soulution number 2 to the store, with GetDrivingRouteAsync working before the upload. The update did work, without any user data being lost, so no problem here.
However, when using the version from the store, GetDrivingRouteAsync is again not working (same problem as in solution number 1).
Seems to be exactly the same issue as this one:
https://stackoverflow.com/questions/32891052/invalid-credentials-with-getdrivingrouteasync-only-when-i-create-packages-for-st

HardwareIdentification.GetPackageSpecificToken API changed in Windows 10

I'm using HardwareIdentification.GetPackageSpecificToken in my app. See following resource:
https://msdn.microsoft.com/en-us/library/windows/apps/JJ553431.aspx
Now, Windows.System.Profile is no longer available in the new Windows SDK 10240. Any idea where I can find it now?
It's available for device family "Desktop" and "Mobile" only. (See https://msdn.microsoft.com/en-us/library/windows/apps/windows.system.profile.hardwareidentification.getpackagespecifictoken.aspx )
So you have to add an Extension SDK. You can do this using the Reference Manager.
See the detailed description how to add an Extension SDK here:
Windows 10 Mobile - cannot hide status bar (StatusBar doesn't exist in context)

Resources