Is it possible to ask a Trigger.io Forge mobile app to close itself through the forge JS api?
We're seeing users having problems with reloads:
We pop up a message when a reload is available, but it's difficult for us to explain that they have to
come out of the app
wait an unknown amount of time (for the reload update to download)
launch the app again
People either don't understand, or the force-quit the app meaning the reload doesn't download, or they come out and go straight back in before it's downloaded - and then see our 'reload' popup message immediately again.
I wondered if we could close the app for them if this would smooth things out a bit. Unless people have better suggestions for this user flow?
Are you listening for the updateReady events to pop up your message? If so, the Reload update has actually already been downloaded and is ready to go: all the user needs to do at that point is switch away from the app and back again; no delay required.
The only way to programmatically close a Trigger.io is in the backPressed event listener, which won't be of use to you in this situation.
Related
I m using Device.BeginInvokeOnMainThread(() => { Thread.CurrentThread.Abort(); });
System.Diagnostics.Process.GetCurrentProcess().Kill(); this in xamarin.forms to kill app in ios through dependency service.
But actually it is not killing the app when i press the home button it is still showing.
Can anyone help me out of this?
This is not possible. From the Apple technical Q&A (https://developer.apple.com/library/archive/qa/qa1561/_index.html):
A: There is no API provided for gracefully terminating an iOS
application.
In iOS, the user presses the Home button to close applications. Should
your application have conditions in which it cannot provide its
intended function, the recommended approach is to display an alert for
the user that indicates the nature of the problem and possible actions
the user could take — turning on WiFi, enabling Location Services,
etc. Allow the user to terminate the application at their own
discretion.
Although the documentation is pretty old, this still stands. Even if you do find some way to implement it, it will never be allowed to the App Store.
I may have the terminology wrong however I am looking for ways to check the queue of meteor.call functions that are being retried due to a user being offline.
Some context: I have a system that allows users to book appointments in a diary. Some users with (very) poor wifi coverage are seeing appointments appear however subsequently disappear and it seems this is due to them being created when offline and then the page reloaded / disconnected before the page comes back online or before the local and remote data are synced. I have implemented an approach to inform the user that they are offline and as such should not change / reload the page however I would like to be able to check this queue so that once the connection is back, I know how long to wait until it has caught up.
Was wondering what the best practice for this is.
If an app that used HealthKit is downloaded, and then the Watch app is started before the iPhone app, HealthKit will not have been allowed yet.
In that instance, the user is going to think the Watch app is broken because no totals or data will be updated, etc.
Is there a best way to avoid this or at least alert the user that you have done or seen?
I'm assuming I'd set some sort of bool that is set to false, and maybe put an alert up on the first screen of the Watch app until HealthKit has been allowed.
Can anyone please so let me know precisely that how can I accomplish the task in which I need to show Push Notification to user when App is Quit/closed?
Currently, I am able to get the push notification done when App is running in background or opened. But App couldn't receive Notification when it is quit/closed by the user.
Right now, it's a really critical task on my shoulders. It's pretty clear do tell me in case if you guys need me to brief in details.
I am having a very hard time to believe that your scenario is Really the following:
When the app is either: open and in the foreground, or open and in the background, you are able to receive a notification to the device, and have its contents displayed in the app, but
When the app is quit (as in not running), the notification does not arrive to the device at all.
I have tested several devices and several push-enabled applications (event source, tag-based). The notification does arrive to the device, after the user subscribed to either a tag or by logging-in (in the case of event source-based), after which sending a notification always arrived to the device.
I don't understand this sentence:
my app logouts with the user
You need to be CLEAR in your explanation. Is there a logout button that the user clicks? If yes, are you also for some reason perform an unsubscribe API invocation? If no, edit the question and provide DETAILED, step-by-step reproduction instructions, AS WELL as provide your application, or any code that you use so that it could be inspected for possible issues.
Iron Router has this awesome method onStop which lets me write code for when a user navigates away from a page. How can write that same code when someone disconnects, like closing the browser, for instance. Thanks
You can only track tab events because the window Javascript API makes this possible.. for tracking the whole browser's close method it would be very intrusive to do so and safe to say that you'll never track it effectively unless you resort to highly intrusive (mostly illegal) methods. One legal way is to convince the user to install a browser extension just for that..