I am implementing C# Metro application in this app, and am implementing this event
DisplayProperties.LogicalDpiChanged += DisplayProperties_LogicalDpiChanged;
statically changing simulator resolution is not firing.
Related
I am writing a React Native app with hardware access. This means that I setup the hardware at application startup. Then I could click "Reload" in the developer menu. But before the code is reloaded I need to tear down my hardware setup since otherwise the setup during restart fails.
Is there any way I can create some kind of callback function/hook that allows me to get informed immediately before app reload? Than I could to the tear down in this function. Please note the code has to run in the handy app (not as a kind of plugin for metro bundler).
I'm developing a react-native app and I'm facing a problem: I need to execute a periodical task (an API call to post some data) in all possible cases: the app is in the background, app is in foreground and app is killed (double tap on the home button and swipe up).
How could I achieve this in iOS?
For Android, HeadlessJS seems to work fine, but for iOS I couldn't find anything which could fit my case.
I've tried with react-native-background-fetch but if the app is killed, also the background fetch is halted (https://github.com/transistorsoft/react-native-background-fetch/issues/34)
I've tried react-native-background-timer, but it works only until the app is killed.
I've also tried adding a geolocation native library to set background mode "location updates" capability, and calling its start method inside the didFinishLaunchingWithOptions into AppDelegate.m. But also this works only until the app is killed.
If I use the same native library on a native iOS app, and I call it inside the same method into AppDelegate.m, it keeps working also when the app is killed.
So which is the difference between the native and react-native app that lets the app survive the force-quit?
I've also tried reading this https://developer.apple.com/library/archive/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/BackgroundExecution/BackgroundExecution.html but I couldn't replicate that info via react-native.
Can someone help me, please?
There we have an web app developed for Android and iPhone (using webview). It is based on Sencha Touch 1.1.1. Thus it runs only on WebKit based browsers, and not on Internet Explorer. I want it to run it on Windows Phone, thus I need to run WebKit (not IE) inside the app (as webview).
Is it possible to build a Windows app with webview which used WebKit?
Running into a strange problem on the Samsung S3 with Sencha Touch 2.2.1. I have an Ext.List control and it sometimes stops scrolling. Any touch on it fires the itemtap and itemsingletap events, but the itemtouchstart, itemtouchend, and itemtouchmoves that usually fire when scrolling do nothing. Again, this happens periodically and once it happens that application (running in PhoneGap) needs to be killed and relaunched.
I haven't experienced the issue on iOS or any other Android tablet. Android release is 4.3 (standard version for S3)
Help!
The local app we have written is not launching in a specific Windows 8 machine only the splash screen appears.
The APP constructor itself is not called.
Note:
This app works in other machines.
We upgraded the OS to 8.1 as well as disabled the antivirus as well.