I am facing a strange issue, appium just flashes white Screen and does not open the app and if i keep the app open manually in the emulator it works. This issue just happen all of sudden.
My Observations on this issue. ( Not aware how to resolve this )
it happens only for few apps like Telegram
in the appium logs i dont see appPackage and Activity ( even though i have set capabilities)
in the logs i see this msg "[UiAutomator2] Neither 'app' nor 'appPackage' was set. Starting UiAutomator2 without the target application
"
in the logs i see " [AndroidDriver] No app sent in, not parsing package/activity "
Solutions I tried:
updated the app
appPackage and Activity is correct
tried clearing the cache of the app / reinstalled it
tried in real device still no luck
Any help is much appreciated
Logs are too lengthy to attach here
its resolved, It was a silly mistake, i had given a different property and in the desired caps i used a different property name (basically the place where i am storing the appPackage and Activity name and where i am using it was different )
Related
I'm facing a strange issue with universal links on iPhone - iOS 12.2.
I'm trying to open the APP using a registered universal link (the same link works on other devices using both - the same and different version of iOS), using identical application (the same version).
What's strange is that I can't even find the option to open the link in a native app when holding the link for a while on this device, although I found it in other devices.
It used to work, but then suddenly stopped to open the APP. I tried rebooting and reinstalling the app.
Did anyone face similar issue? Any suggestion in debugging? I'd really like to avoid factory reset of the phone.
You might be running into either of these two bugs:
https://openradar.appspot.com/45201697
https://openradar.appspot.com/33893852
I just ran into this. Deleting the app, reboot the device, wait an hour or so (unsure of time needed to wait) then reinstall the app. That seems to force it to re-check the AASA.
Seems like there could be a process running after reboot blocking swcd from running.
Have you tried to delete the app and restart the phone to check if this is not a apple-app-site-association problem?
So after upgrading to the newest iOS the problem still remained in Chrome.
I was able to open the contextual menu and open the app through the Open in... item from Safari, and since then it works as expected across all the browsers. This doesn't explain the origin of this issue, but I hope this will help you as well.
I am encountering a strange situation with a simple application I develop. When I deploy the application using Xcode (with debugger attached), it works perfectly.
When I close Xcode, disconnect the phone, kill and restart the application, it works just fine, too! For several hours that is.
After some time (usually the next day morning) when I try to open the app up, it immediately fails. A white rectangle filling the screen animation does happen, but when the application is supposed to flash its UI in, it quits instead.
How can I get ahold of the crash logs from the iPhone? Does it store any? This application is not from the AppStore, it's my development application installed through Xcode.
When I re-deploy it after finding this has happened again, hoping I'll get something with a debugger attached, it starts working again. This has happened to two of my apps.
You could try to look into your device's logs: Window->Devices -> Select your device-> Click 'View Device Logs'. Find your app crash there and on the right side you should see a crash report.
I've got an app that uses Core Data that sporadically stops launching so I have to reinstall it using XCode and then it launches again like normal for a while, with all the Core Data information still preserved.
I have seen that an app often stops launching when the target of an app is too low in comparison to the device software version, however this is not so for this app and device (iPhone 6s).
Have you had such an issue before? What do you think could be causing this problem?
There are many, many, many things that could cause an app to fail to launch. You need to narrow things down and collect some data so that you can find out what the problem is and do something about it. Right now you don't even know that it's related to Core Data, you're just guessing.
For a crash on launch, look at the device console and see what messages appear when you try to launch the app and it fails. You can get the device console messages by
Connecting your device to your Mac
Opening Xcode's "Devices" window (cmd-shift-2)
Looking in the bottom half of the window
A better way to watch the console is to use the free iOS Console app.
The problem was that, as mentioned by dan in the comments, the code was being signed for a short period of time (7 days) and so I had to keep re-installing it on the iOS device to keep it working. Thus to keep the app working indefinitely a paid developer account is needed.
Also mentioned in this reddit forum:
https://www.reddit.com/r/jailbreak/comments/4hotx3/news_free_developer_account_installs_reduced_to_7/
A user has reported that my app suddenly won't launch on their device. They sent me a video, and they launch the app, the launch image screen shows for a split second, but then crashes back to the iOS home screen.
The user tried deleting and reinstalling the app with no benefit.
I use Crashlytics, and am not getting any reports of crashes from them (or any other user- although I've seen them in prior versions so I know it's working correctly). I'm also not seeing any crashes in iTunes connect.
I asked the user to send me any crash reports in the Settings Diagnostics section and they said there are none listed for my app.
I have confirmed that their iOS version is supported by my app. (iOS 8.4).
I'm not sure where to go next, and would appreciate any pointers. Sorry for the vague question but I have posted everything that I know about the situation.
Just wanted to provide some closure on this. The user ended up wiping and restoring their device, and it solved the problem. It seems extreme to me but it was their own suggestion and didn't take them long to do. So I'm not sure what caused this but that's one (albeit brute force) way to fix it.
So I'm trying to make an application using the DJI SDK. In order for my app to function properly, my iDevice needs to be hooked up to the remote controller of the drone via USB.
This means I can't also run the app via xcode and get console output.
Is there a way of saving console output when using an app on your phone? I am aware of the crash logs, but sadly they don't provide enough info to be useful to me.
This problem started when I got a runtime error only when the device was connected to the remote controller. Therefore there was no way of isolating the problem since I couldn't tell what went wrong.
Another solution would maybe be a 1 female to 2 male usb chord, but I haven't found one online yet and even if I did I don't know if that would work.
Is there a standard way of debugging when using hardware that needs to be connected to the device?
from Xcode, hit window on the tool bar at the top, then Devices. Select the device you want to read the log from. However, this is the log for the entire phone, and you have to be plugged into the mac... so you'll have to run your tests, unplug from the DJI, plug into the mac, go to devices, and scroll through the log until you find the output from your app, and you won't be able to see real time expected outcome.
It's not ideal, but that's the only way I know of to see the apart from building an entire console log into your app yourself.