I get this issue on one of my screens. The expo project runs 100% fine on web build and runs well on the other screens on android and ios.
Related
My problem seems to be very straight forward, yet very confusing. I have a wrapper Xamarin Forms application for my web app. The Xamarin app as expected, is just a WebView rendering the said web application.
On my web app, I have a HTML file input
<input type="file" accept="image/*,application/pdf;capture=camera">
When the webpage is accessed using the web browser (Android/iOS) it works as expected and provides the user with an option to use their camera for the picture. On the iOS version of the Xamarin Forms app, everything seems to be fine with the user still being presented an option to use their camera.
But on the Android version, I cant seem to get it to work. I have added the camera permission <uses-permission android:name="android.permission.CAMERA" /> in the AndroidManifest.xml. Added run time checks to ensure the user either has already or can now agree to giving camera access to the app.
Not sure what I am missing but the camera option does not seem to open up for the Android version. I have seen some articles about WebRTC and using a custom renderer but not sure how and where to processed with those. Any suggestion to get this to work would really help
Having problem not showing the ffimageloading image on the listview on iOS12.1.3 later by the client and it happened many time even though not always but it works on my local ipad, which i am not sure how to tackle.
Now it looks like also affecting the android devices. The client used to be working and it's now not working
I have initialize the init function in AppDelegate which is required otherwise my device also won't see.
Only thing i have inside was an delayloading and downSampleToViewSize which i am not sure what cause it.
having an issue with Square POS Web API on Android.
We are trying to implement a kiosk app and the kiosk browser is Android based.
If run in Chrome browser the Square app loads fine with no error however if loaded in an Android browser (eg Dolphin) it fails with the following error.
Point of Sale API must be started with startActivityForResult() in the same task. It looks like the caller either used startActivity() or used startActivityForResult() from a finished activity or with the FLAG_ACTIVITY_NEW_TASK flag.
How can we fix this so the app can be used in kiosk apps that use android browser?
Square POS Web API only works with Chrome intents. Therefore you must use the Chrome browser with your Android device. We are in the process of updating our documentation to reflect this information, sorry for any confusion!
I have Xamarin Live Player up and running.
When I use it with a newly created Xamarin Forms (Master Details) app, it works fine. I see the app on the device.
However, when I try to run my full-blown app, Visual Studio tells me "Deployment to device failed. Make sure that Xamarin Live Player is open and that the device is in the same network."
Since the new app runs fine, I guess something else is the problem.
I've already set the Android project properties to be same as the newly created app.
Just to make sure, I've made it so that my full-blown app requests all rights.
How could I debug more in detail what's going wrong?
Xamarin Live Player can't run all apps. As soon as you use reflection, embedded resources, a MVVM framework or a custom renderer in Xamarin.Forms it might simply just not run the App.
You can read about the limitations of Xamarin Live Player in the official documentation for it.
You will probably have a much better experience just running directly on the device without Live Player.
I need to detect user's inactivity time in NativeScript app.
I tried with few plugins (like ng-idle) but they are not compatible with NativeScript.
I also tried to to emit application level event (in page router outlet) but it is not working either.
Any help will be appreciated.
In the mobile context, you would like to track the inactivity in the native mobile application lifecycle. For Android, you can extend the Application and implement some of the solutions shown here. Following this approach, you can do the same on iOS (overwrite the AppDelegate as shown here and implement some of the native solutions)