ViewIsDisappearing gets called when we pull down the Notification Tray and ViewIsAppearing is called when we push the Notification Tray up.
This happens after upgrading our Xamarin Forms version to 4.8.0.1364 from 4.1.0
How do I prevent the calling of ViewIsDisappearing/ViewIsAppearing when the app is in Inactive state ? This was not there till 4.6
It has to be some other library triggering it, I just created a new project and tested but it the notification trail didn't trigger any of those events
Related
In Xamarin iOS , when the api call starts requesting, when we switch app to background or the notification panel is drawn from the top, suddenly api call fails. Api returns bad request.No issues with foreground calls. This does not happen in android. api calls will be successful in background. When DidEnterBackground method has hit, api call will be failed by the time.I am using iOS OS 13.6 device. Forms has the latest version.Please help...
In the iOS build settings,Changing the HttpClient Implementation option from NSUrlSession to Managed fixed the issue!!!
I am using latest leanback version 27.0.0 in my app. Now am facing few key issues which was not there in the older version 24.2.1. The issue is like this.
I have registered the key events. So every time when I press "OK" buttons with the remote onKey() method will be called. but when I pause my app by pressing android home and resume it again onKey() method is not calling. But on resume, the key will be registered only.This issue was not there when I was using the older version of leanback.
Thanks in advance.
I'm running into an issue with push notifications using Nativescript and Onesignal
Onesignal keeps telling me the app is missing push notifications in xcode.
But when I run the app, I do get the 'appname would like to send you notifications' message and under xcode everything seems to be set correctly.
I tried deleting the platforms folder, rebuilding the app and so on, but it remains the same message. When I change the app version, I do see the app version change on the onesignal platform, so the informations is passing but apparently apple does not let the notifications through.
Anyway to debug this? How can I be sure the app has push capabilities?
I recently released a new version of my app which now contains some code which at run time, checks for a new version of the app. If a new version exists, an alert will appear asking the user if they want to download the new version now or later. This notification appears when user opens app app, and if they say no will not appear again, until app process is killed and then opened again. So the notification is not intrusive
However Apple rejected my app saying
"Your app includes an update button or alerts the user to update the app. To avoid user confusion, app version updates must utilize the iOS built-in update mechanism. "
There are frameworks online you can add to your app like this
https://github.com/ArtSabintsev/Siren
Which do this, and I believe clash of clans notify users when app update is available. So how come my app is being refused for this feature.
Is there another way I can notify users that a version of the app is available that will not cause the app to be refused.
Any info would be much appreciated
I am using Xamarin.Forms.Labs to send SMS messages from my app. It works great on WP and Android but with the iOS it opens up the default texting screen and allows you to send a text but then I am unable to get back to my app. I click cancel or the iPhone button and reopen my app and it is still on the texting screen. Any ideas what I could be doing wrong or why it doesn't return to my app once I have finished texting? Is anyone else having this issue?
This was a bug in the iOS implementation. I just pushed a fix for it and you can use the latest code (master branch) to test it out.
https://github.com/XLabs/Xamarin-Forms-Labs/pull/498
I will get it included in the next release package.