I recently had to switch to the bare workflow from the managed workflow. After running expo eject I tested on android, which suffered from an issue with expo-constants not being available, after installing that it worked just fine. I moved on to installing it on the iOS simulator and got an error trying to install. Been trying to debug it but not having any luck. Logs are below:
success Successfully built the app
info Installing "/Users/***/Library/Developer/Xcode/DerivedData/***-dtoeptcccdubmbcvblrjlzhwexaq/Build/Products/Debug-iphonesimulator/***.app"
An error was encountered processing the command (domain=IXUserPresentableErrorDomain, code=1):
This app could not be installed at this time.
Could not install at this time.
Failed to chmod /Users/***/Library/Developer/CoreSimulator/Devices/8666E576-E2C9-4711-B8EB-2A7720C08B84/data/Bundle/Application/F519E6C9-3AFC-49F4-B0E5-9D40C41F54D6/***.app/*** : No such file or directory
Underlying error (domain=MIInstallerErrorDomain, code=4):
Failed to chmod /Users/pedromcunha/Library/Developer/CoreSimulator/Devices/8666E576-E2C9-4711-B8EB-2A7720C08B84/data/Bundle/Application/F519E6C9-3AFC-49F4-B0E5-9D40C41F54D6/***.app/*** : No such file or directory
info Launching "com.***.***"
error Failed to launch the app on simulator, An error was encountered processing the command (domain=FBSOpenApplicationServiceErrorDomain, code=1):
The request to open "com.***.***" failed.
The request was denied by service delegate (SBMainWorkspace) for reason: NotFound ("Application "com.***.***" is unknown to FrontBoard").
Underlying error (domain=FBSOpenApplicationErrorDomain, code=4):
The operation couldn’t be completed. Application "com.***.***" is unknown to FrontBoard.
Application "com.***.***" is unknown to FrontBoard.
I redacted any sensitive info with ***. It says that the build was successful but after looking into the build itself I don't see any executable. Here's the folder contents of the .app package.
Any help is much appreciated.
Related
i cant insatll main google app(package: com.google.android.googlequicksearchbox) from play store on my android vivo y15s android 12.
on android the error was something about package name conflicting.
then i tried to install the apk file from CMD of google of version 13.48.11.26.arm64 then it showed the error...
adb: failed to install google.apk: Failure [INSTALL_FAILED_DUPLICATE_PERMISSION: Package com.google.android.googlequicksearchbox attempting to redeclare permiss ion com.google.android.apps.now.OPT_IN_WIZARD already owned by com.google.androi d.apps.searchlite]
then i uninstalled the com.google.android.apps.searchlite] but nothing changed...same error
then i tried to uninstall com.google.android.apps.now.OPT_IN_WIZARD then error occured
Failure [DELETE_FAILED_INTERNAL_ERROR]
Hi am working on expo project while I try to run my project, am facing issue.
`> Task :app:exponentPrebuildStep FAILED
Execution failed for task ':app:exponentPrebuildStep'.
A problem occurred starting process 'command './node_modules/expokit/detach-scripts/run-exp.sh''
`
Cause: error=13, Permission denied
I don't know how to fix it, tried clean, invalidate caches, rebuild but everything is working fine but when I give expo start -c and run my project then am facing this error and I tried expo publish rerun my app but I don't know why this error is coming MacBook.
This is the error:
Unable to resolve "expo-av" from "node_modules\react-native-gifted-chat\lib\ExpoMessageVideo.js"
Failed building JavaScript bundle.
#Jaime, I had the same issue.
I did the following and the issue is resolved
What did I do?
1.In my computer, opened the command prompt
2.changed the directory to the project directory
3.In the command prompt, ran the following command
expo install expo-av
4.Closed the command prompt
5.Started the project , ran the simulator and could see the app running
When attempting to launch an Expo project from the XDE, I am presented with the following issue where the Expo simulator app will not install:
Error running xcrun simctl install booted
/Users/username/.expo/ios-simulator-app-cache/Exponent-X.Y.Z.app: An
error was encountered processing the command
(domain=NSPOSIXErrorDomain, code=22): Failed to install the requested
application The bundle identifier of the application could not be
determined.
Ensure that the application's Info.plist contains a value
for CFBundleIdentifier.
Error installing or running app. Error: Process exited with non-zero
code: 22
Which will display like the following image in the XDE:
This appears to be a corrupted or incompatible version of the simulator app that is stored on your computer. The Expo Development Environment (XDE) does not resolve this issue automatically.
As mentioned on the Expo and XDE forums, the way to resolve this issue is to navigate to:
~/.expo/ios-simulator-app-cache/
In the Finder, and delete the file Exponent-X.Y.Z where X, Y, and Z represent the version of the app.
Source: https://forums.expo.io/t/error-installing-expo-on-ios-simulator/741
I am deploying a RoR app to our production environment.
App 9676 stdout: Rendered users/check.pdf.erb (15.9ms)
App 9676 stdout: Completed 500 Internal Server Error in 178ms
App 9676 stdout:
App 9676 stdout: RuntimeError (Error: Failed to execute:
App 9676 stdout: ["/home/deploy/.bundler/customerportalapp/ruby/2.1.0/gems/wkhtmltopdf-binary-0.9.9.3/bin/wkhtmltopdf", "-q", "file:///tmp/wicked_pdf20140827-9676-6sbtcf.html", "/tmp/wicked_pdf_generated_file20140827-9676-1qunpjr.pdf"]
App 9676 stdout: Error: PDF could not be generated!
App 9676 stdout: Command Error: /usr/local/lib/ruby/gems/2.1.0/gems/bundler-1.5.3/lib/bundler/spec_set.rb:92:in `materialize':
Could not find rake-10.3.2 in any of the sources (Bundler::GemNotFound)
I think the error "Could not find rake-10.3.2" is a red herring. Rake 10.3.2 is installed.
I am at a loss as to where to start troubleshooting the error. Any suggestions?
I had a similar issue with wkhtmltopdf, where bundler couldn't find rake even though it was installed. I tried debugging this for a full day and gave up trying to find and fix the cause.
This workaround is the only thing that made it work for me.
bundle --deployment
It will bundle your gems in a .bundle folder in your app, making them reliably accessible to bundler.