I am currently building an Ionic App and testing it out with genymotion emulator and I found out an issue.
With Android devices that is 4.3 and below, my ng-show expressions work fine and show when need to and hide when need to but if the Android device is >4.3 i.e. 4.4.2 nd so son... All ng-show expressions do not fire or do not catch at all.
I dont know if anyone has encountered an issue like this before or if anyone has a good theory why this is happening.
Thanks
Related
I'm developing a Spotify-app on Android. The app already runs on Nougat and Oreo, but I'm still having problems with Android 6.0.
The Problem is if I install the app via Playstore, I'm stuck on the loading screen because I don't receive a correct response.
But now, if I install the exact same app from Android Studio, it works without any problems. This also makes debugging very difficult, because I can't use the debugger for Playstore apps.
Do you have any Ideas why? I've got the same problem on all 3 devices that run Android 6.0
I don't really have an answer for that, but I can't even get that far. Which Spotify API are you using? If you're able to get it to get that far, I may have hope haha
I'm trying to teach myself JavaScript by creating an little puzzle/game app with Cordova. I've got a basic prototype thing working, and have successfully got it to build on iPhone, and it runs perfectly.
I have 3 android phones to test with, 1 Marshmallow (BLU branded), 1 Lollipop, and 1 Kitkat... and the app works perfectly on those as well. I sent the app to 2 friends on the other side of the country to test, and it crashes on their Samsung Marshmallow phones ( a Galaxy 7, and a Galaxy Edge 7). It runs for a bit, and then just crashes without any user input.
So, I tried 2 separate crash analytics plugins, Fabric and Crittercism. I can verify that both of these are working, as I can force a crash in the app, and it shows up as a crash report.
But when my friends run the app with the crash analytics, whatever is going on that makes the app blowup, it isn't triggering any reports from Fabric or Crittercism. I've tried to get the android emulator running on my PC, but unfortunately it is an AMD processor, which is missing some necessary virtualization. I can't even get the super slow ARM version of the emulator to run on my PC, it just hangs forever.
I just recently installed cordova, and took all the defaults during setup. So from what I can tell, it should be targeting android API 23 (Marshmallow). But maybe there's some other kind of build issue that is messing things up?
So I'm kind of at a loss of how to debug this problem. Short of finding someone locally who can lend me a Samsung Marshmallow phone to debug with, I can't think of anything else that would work. Does anyone have any ideas?
The ARM emulator is indeed excruciatingly slow. I would suggest a third-party emulator. I use GenyMotion (which uses VirtualBox under the hood). You might have some luck with that. Alternatively, ManyMo is a cloud-based solution that might prove useful.
The system web view used by PhoneGap/Cordova will vary widely across Android devices, which means you can run into different issues across Android versions and device manufacturers. I suggest using the Crosswalk plugin to mitigate those problems. Do note that this will increase the size of your APK and footprint of the installed app on your device.
When the app crashes, does it actually crash to the launcher, or does the app reload itself (or just show a background color)? I wouldn't expect Crashlytics to handle JavaScript issues unless the JavaScript caused the app to crash out to the launcher.
I use MUPDF to view pdf files in an Android app. The app works fine with Samsung s6 and Nexus 5 (Android 5.x). However when using Samsung S3 (Android 4.3), it just breaks without saying anything in the debugger "the app just disappears without saying any". Is that regarding MUPDF lib? I know this lib has compiled native code. As it is a legacy code and I have to deal with it, what could be the approach to solve such issue?
Thanks.
Check the Android logcat output when the app dies, that should reveal what is happening. You may need to run the app outside the debugger to get the full logcat output. If you can get this, please edit your question to add the output.
Depending on which debugger you're using, you may need to explicitly enable native debugging if you haven't already.
MuPDF isn't legacy code, its continuously being developed. I'd suggest you open a bug report, that way you stand some chance of informed people being able to help you.
I have an application in android which gets some information from source code of some websites
it is working well on the emulator but it does not work on my real device (Galaxy S2)
**please notice that it is not working on real device(contrary to previously asked questions)
Any ideas where is the problem?
I found the answer:
I was using 2.3.3 version of OS in avd. the device i have tested my app was 4.
the problem solved using AsynkTask class which should be implemented in apps that they are using os versions greater than 3 when you need to get anysthing from web or connecting to database...
I think this link have a good explanation:
Why Ice Cream Sandwich Crashes Your App
I developed an app using phonegap 2.1.0, everything works perfectly fine in Iphone and Android 2.3.x and 4.0.x. However when I run my app in Android 4.1.2 (Jelly Bean, Galaxy Nexus), text inputs stop working after a few strokes.
I have searched on the web (dozens of results) and it seems to be a common problem, no solution has been provided for this... NONE!
Phonegap team says that this bug is fixed since phonegap 2.0.0, but clearly this is not true.
I know there is a similar question in SO, tried that already and didn`t work. Any ideas?