I've been trying to troubleshoot the issue I am having after I changed my computer with getting .apk file to run properly. I have read all the various solutions, but none worked so far.
I continue to get this error can can't figure out why:
Starting calabash-android console...
Loading /Users/sasaro/.rvm/rubies/ruby-2.1.2/lib/ruby/gems/2.1.0/gems/calabash-android-0.5.2/irbrc
Running irb...
irb(main):001:0> start_test_server_in_background
RuntimeError: App did not start
from /Users/sasaro/.rvm/rubies/ruby-2.1.2/lib/ruby/gems/2.1.0/gems/calabash-android-0.5.2/lib/calabash-android/operations.rb:609:in block in start_test_server_in_background'
from /Users/sasaro/.rvm/rubies/ruby-2.1.2/lib/ruby/gems/2.1.0/gems/retriable-1.3.3.1/lib/retriable/retriable.rb:31:inperform'
from /Users/sasaro/.rvm/rubies/ruby-2.1.2/lib/ruby/gems/2.1.0/gems/retriable-1.3.3.1/lib/retriable/retriable.rb:59:in retriable'
from /Users/sasaro/.rvm/rubies/ruby-2.1.2/lib/ruby/gems/2.1.0/gems/calabash-android-0.5.2/lib/calabash-android/operations.rb:608:instart_test_server_in_background'
from /Users/sasaro/.rvm/rubies/ruby-2.1.2/lib/ruby/gems/2.1.0/gems/calabash-android-0.5.2/lib/calabash-android/operations.rb:125:in start_test_server_in_background'
from (irb):1
from /Users/sasaro/.rvm/rubies/ruby-2.1.2/bin/irb:11:in'
What am I doing wrong? What am I not seeing? Is there a solution?
On Mac OS X 10.9.4. The app get's reinstalled when I run reinstall_apps, and when I run start_test_server_in_background I see the app open in the emulator. But, then I get the above error. The app is still usable and running in the emulator.
I'm new at calabash install so please be gentle and detailed if you have come across anything like this.
Try running this command:
calabash-android resign path/to/file.apk
Delete all Test_Server, delete android app from folder and copy new one after that
Try to:
calabash-android console app-debug.apk
irb> reinstall_apps
irb> start_test_server_in_background
it should start
and after that if it wont recognise server try calabash-android resign app-debug.apk
and calbash-android run app-debug.apk
Delete the test_server folder and resign your apk file
calabash-android resign path/to/file.apk
Then open the console
calabash-android console path/to/file.apk
and
reinstall app by typing
reinstall_apps
then start your app
start_test_server_in_background
Related
Now command npx react-native run-android work in Windows command line, but when I try call it in PhpStorm Terminal:
"adb" Ґ пў«пҐвбп ўгв॥© Ё«Ё ўҐиҐ©
Є®¬ ¤®©, ЁбЇ®«пҐ¬®© Їа®Ја ¬¬®© Ё«Ё Ї ЄҐвл¬ д ©«®¬.
info Launching emulator...
info Installing the app...
error Failed to launch emulator. Reason: No emulators found as an output of `emulator -list-avds`.
warn Please launch an emulator manually or connect a device. Otherwise app may fail to launch.
Before I reinstalled Windows, it worked fine. I don't understand what I forgot to configure. Where could be the problem?
I just reinstall IDE and problem went away.
Probably it's too late but it may still help others.
"adb" Ґ пў«пҐвбп ўгв॥© Ё«Ё ўҐиҐ©
Є®¬ ¤®©, ЁбЇ®«пҐ¬®© Їа®Ја ¬¬®© Ё«Ё Ї ЄҐвл¬ д ©«®¬.
Is actually a Russian equivalent of
'adb' is not recognized as an internal or external command, operable program or batch file
affected by some encoding issues.
It means that you need to add the path to your adb file to the System PATH variable and then restart the IDE.
adb should be located in the platform-tools folder of your android SDK.
Sometimes, while Espresso testing, I see the following exception.
Test instrumentation process crashed. Check package_name.TestName#methodName.txt for details
Where is this .txt file stored? I can't seem to find it anywhere.
Use Case
In Jenkins (CI), I want the logs to see exactly what stacktrace caused the crash.
If you are working with an emulator, in A.S open Device File Explorer and go to:
/data/user_de/0/android.support.test.orchestrator/files/, then you can look for a particular file there
EDIT: June 25 - 2019 >> If you have updated to AndroidX dependencies, then the .txt file is located in
/data/user_de/0/androidx.test.orchestrator/files/
In my case, it was simpler to just check Logcat, rather than listen to that recommendation
For others encountering this issue, as #antek pointed out the files might not be accessible on a non-rooted device. You might try using an emulator running a non-Google Play API where you can obtain a root shell.
adb root
adb shell
ls /data/data/androidx.test.orchestrator/files
Alternatively, you could try running the tests using the debugger.
I could not find the text file, but I was able to get logcat and view the fatal that caused the orchestrator to crash
first I clear the logcat
adb logcat -c
then I run the test, then I grab the logcat
adb logcat > ~/Desktop/logcat
then I open logcat file and search for string FATAL
I just did wipe data in Android studio for my emulator using Device manager.
Restarted the emulator and run the test works for me
I am running on Windows 10:
Permission to the folder is Everyone & Full Access.
Cmd line is set to Administrator.
--version react-native-cli: 2.0.1
--version react-native: 0.47.2
* What went wrong:
Execution failed for task ':#myApp/react-native-spinkit:mergeReleaseResources'.
> java.io.IOException: Could not delete path 'C:\Users\My\Desktop\App\node_modules\#myApp
\react-native-spinkit\android\build\intermediates\res\merged\release\drawable-xhdpi-v4'.
For example, I will get the error above. Sometimes it says could not delete some intermediate path, sometimes, it says it could not create them.
It is not a fixed error output, intermediate folders that got into trouble is different every time. When I repeat React-native run-android on the good days 2-3 times, it will compile successfully. On the bad days I will repeat the cmd 10-15 times, then it suddenly works.
By the way, I use android/gradlew clean command to make sure it does the cleaning, too.
One thing I noticed is that every time it fails the compile percentage % gets a bit further. Until the end if I see 100% then it will work.
The same code compiles in one go with Mac, android physical or virtual machine, same thing on Mac is very stable. This problem only happens with my Windows setup. Anyone experiencing the same thing as me? Is there anything I can do to fix this issue?
You can try this: Error:Execution failed for task ':app:processDebugResources'. > java.io.IOException: Could not delete folder "" in android studio
Deleting the /build folder did it for me.
I guess some of the files in the target build directory is open in another tool you use. Just a file handle open in the folder which has to be cleaned. The build task 'clean' wants to delete all the files in the build directory(normally 'target') and when it fails, the build fails.
This worked for me:
cd ./android && ./gradlew app:assembleDebug && ./gradlew installDebug
for some reason I can't seems to run any project on my device.
For the experiment, I've created a new empty blank project named it: emptyApp.
I've deleted any certificate I had in Apple Developer webSite and start from scratch.
I've created developer certificate and download it -> save it to keychain
New app ID for my emptyApp, double checked the bundle ID.
New provision Profile for my app and download it with my device enabled inside the certificate.
So i've got a new project, with all the right settings and i'm getting this error:
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Couldn't posix_spawn: error 1'
Command
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-stdlib-tool failed with exit code 6
Now I can Kill myself, but why i'm keep getting this error ?
I've did everything according to the book, and it's amazing I can't seems to run an empty project on my device (iPhone 6 plus).
any suggestion how to fix this error?
I had this problem after changing my apple id. Here is what i did.
Go to xcode -> select your project -> Build Phases -> open "Compile Sources" and "Copy Bundle Resources". Check if any files are listed in red color. If so , just delete it. Then clean and run.
You might have to restart (idk why but it worked for me).
Hope this helps.
In my case i changed my apple id and i had to redo the whole generating dev, sign in etc certificates. Its finally working on my device. It used to only work on the simulator
Code 6 means Code Sign error (system file).
the solution is to bring this file from backup or reinstall your current OSX.
Just restart your mac, that worked for me.
My app is for the iPhone only .And it is working fine on all devices but when submitted the app it get rejected by apple by saying .......
On 1st time submission
We found your app crashed on launch so we were unable to review it.
Please revise your app and test it on a device to ensure it will launch without crashing, and that it runs as expected, before resubmitting.
this the crash report link please
this is the crash report
crash report
on second submission it get rejected they says
Thank you for your resubmission. However, we were still unable to review your app, as it crashed on launch. We have attached detailed crash logs to help troubleshoot this issue.
Specifically, upon review we found the application will shortly crash after launch.
they send crash report
on second time submission
on second time submission
I didn't get where i am doing wrong ,please check this ,Thanks in advance
I also try Bhavin step to find the crash location but terminal show's me like that
I found the solution. We can just directly drag and drop the crash-report on the device log.
Then it will convert the crash report into readable format.
STEPS:
Attach your device to mac.
Open Xcode
Goto window from menu bar
Click on devices like this
Now, drag and drop your crash report you received from apple. It will symbolicate it and show you in readable format. If the file extension is .txt, change it to ".crash".
Follow these steps :
Get the .ipa file that you submitted to the app store.
Rename the extention .ipa with .zip , extract it. You'll get a Payload Folder which contains .app file.
Create a folder with this .app file and crash log file.
Now, open terminal application and go to the folder created in above step (using cd command).
Run this magic line :
atos -arch armv7 -o YourAppName.app/YourAppName MEMORY_LOCATION_OF_CRASH
Where, MEMORY_LOCATION_OF_CRASH = location where your app crashed as
per the report.
It'll give you the exact line, method name which resulted in crash.
If you test your app and it works fine but Apple keeps rejecting it then you need to test it on release mode not debug mode as follows:
Edit scheme > Run > Build configuration > release
Hope this helps someone because I came across this issue and it took me too long to sort it out!