I have implemented an Interactive Message Button and when pressed, the response is an update of the message.
In the Desktop app it works fine. But in the Browser I have to refresh to see the update. I think this is a bug because it does not make sense to update the post when the user does not see the update.
The update problem got solved as we upgraded to Mattermost 4.4.3 .
Related
The OneSignal site goes through great detail on launching the prompt for browsers, but I'm either overlooking the option for mobile or that option doesn't exist.
I'm using Ionic 4/Angular 8 with the cordova-onesignal plugin. I've tried OneSignal.showNativePrompt() but that method doesn't exist on OneSignal. I've also tried this.oneSignal just to see what functions are available and read the comments, but there doesn't seem to be anything that triggers the prompt.
Is there some other way using Ionic to trigger the message to allow users to subscribe to notifications?
Never mind!
Guess I overlooked the promptForPushNotificationsWithUserResponse() function. Looks like it is a promise so you can perform your full suite of setup after it resolves.
This morning, when I logged in to the Data Factory UI, I was presented with the following message:
I clicked "Cancel" as we weren't quite ready to upgrade at the time, but now that we have ensured that all our PowerShell scripts, etc. are unaffected, we want to perform the upgrade. Unfortunately, I can't find anywhere in the ADF UI nor in the Azure portal, where we can initiate the upgrade, and the message box no longer shows up when logging into ADF. How do we proceed?
There should be a banner on top of your authoring screen that has the upgrade button. If that's not showing please refresh your browser and the banner should show up again :)
Let me know if this solves it.
I have been seeing this error when trying to login to my app.
It is using the mfp auth framework
any explanation of what this is would be very helpfull
I see this in the simulator, I don't see this on the device, but wl.connect() always fails in the device
This was due to direct update, anytime a direct update happens i get this error, then i have to shut down the app and restart it
I had the same issue in simulator, deleting and reinstalling the app fixed this.
I'm trying to reach TestFlight on iTunesConnect but it keeps only the loading spinner and do not show anything. I've tried with Chrome and Safari without success.
http://prntscr.com/8sv799
In my other application on the very same account everything works correctly.
I've already written to support waiting for their response.
My issue was resolved from the support team. They didn't provide me full details what caused this, however after sending them needed information(including page source code) they fixed it on next day.
So if you experience the same, I advise you to contact them(via iTunesConnect).
I'm trying to get device token in iPad for remote push notifications;
registerForRemoteNotificationTypes is called okay, no error, but didRegisterForRemoteNotificationsWithDeviceToken also not been called;
Application is appear in Settings/Notification;
What's I doing wrong?
iPhone is registering successfully.
Thank you
PS: iPad 1, iOs 5.1
In this case, if the code works on iPhone that code should work on iPad as well. Coz the os is same. Anyway if your code is not working on iPad try to remove provisioning profile from the iPad and reinstall the correct one. Sometime the old provisioning profile remains. And don't forget to check the code signing on target as well.
check that you are registering correctly for Push Notifications, including verifying your provisioning profile for "aps-environment" key and the code signing of the .app.
also you can debug Push Notification status messages in the console (you will need to install PersistentConnectionLogging.mobileconfig provisioning profile on your device and reboot it. check out this link under "Observing Push Status Messages").
There is an important thing to know with the provisioning profile. You should ensure to create the certificate first (the one used for the notifications), and then recreate the provisioning profiles, so that they know about the notifications. So you're sure it's not a provisioning profile issue.
Well, problem was solved in production sign and provisioning, but not in development. When I archive application for device and load it through iTunes, push notifications is working. Very strange behaviour.
I know it's a late answer, but it may help others. I had the same issue as the OP. After you click ok on the notification popup, it disappears but none of the method gets called to get the device token. Then I checked the internet connection when testing push notifications and I realized I had no connection. After re-connecting, it began working fine.