Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can run on sim but fails on eas build #15

Open
nosnaj opened this issue Nov 23, 2023 · 6 comments
Open

Can run on sim but fails on eas build #15

nosnaj opened this issue Nov 23, 2023 · 6 comments

Comments

@nosnaj
Copy link

nosnaj commented Nov 23, 2023

image

Not sure what went wrong here...

In text:

› Copying   ios/BeaconHangOutMore/GoogleService-Info.plist ➜ ./GoogleService-Info.plist
› Copying   ios/BeaconHangOutMore/Supporting/Expo.plist ➜ ./Expo.plist
› Compiling BeaconHangOutMore » SplashScreen.storyboard
› Preparing BeaconHangOutMore » Info.plist

❌  (ios/Pods/Target Support Files/Pods-BeaconHangOutMore/ExpoModulesProvider.swift:19:8)

  17 | import ExpoLinearGradient
  18 | import ExpoSMS
> 19 | import ReactNativeWidgetExtension
     |        ^ no such module 'ReactNativeWidgetExtension'
  20 | #if EXPO_CONFIGURATION_DEBUG
  21 | import EXDevLauncher
  22 | import EXDevMenu
▸ ** ARCHIVE FAILED **
▸ The following build commands failed:
▸ 	SwiftCompile normal arm64 Compiling\ ExpoModulesProvider.swift /Users/expo/workingdir/build/ios/Pods/Target\ Support\ Files/Pods-BeaconHangOutMore/ExpoModulesProvider.swift (in target 'BeaconHangOutMore' from project 'BeaconHangOutMore')
▸ 	SwiftCompile normal arm64 /Users/expo/workingdir/build/ios/Pods/Target\ Support\ Files/Pods-BeaconHangOutMore/ExpoModulesProvider.swift (in target 'BeaconHangOutMore' from project 'BeaconHangOutMore')
▸ (2 failures)
2023-11-21 10:28:45.570 xcodebuild[34960:43004] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
** ARCHIVE FAILED **
The following build commands failed:
	SwiftCompile normal arm64 Compiling\ ExpoModulesProvider.swift /Users/expo/workingdir/build/ios/Pods/Target\ Support\ Files/Pods-BeaconHangOutMore/ExpoModulesProvider.swift (in target 'BeaconHangOutMore' from project 'BeaconHangOutMore')
	SwiftCompile normal arm64 /Users/expo/workingdir/build/ios/Pods/Target\ Support\ Files/Pods-BeaconHangOutMore/ExpoModulesProvider.swift (in target 'BeaconHangOutMore' from project 'BeaconHangOutMore')
(2 failures)
Exit status: 65
+-------------+-------------------------+
|           Build environment           |
+-------------+-------------------------+
| xcode_path  | /Applications/Xcode.app |
| gym_version | 2.213.0                 |
| sdk         | iPhoneOS16.4.sdk        |
+-------------+-------------------------+
Looks like fastlane ran into a build/archive error with your project
It's hard to tell what's causing the error, so we wrote some guides on how
to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
Before submitting an issue on GitHub, please follow the guide above and make
sure your project is set up correctly.
fastlane uses `xcodebuild` commands to generate your binary, you can see the
the full commands printed out in yellow in the above log.
Make sure to inspect the output above, as usually you'll find more error information there
[!] Error building the application - see the log above
Error: The "Run fastlane" step failed with an unknown error. Refer to "Xcode Logs" below for additional, more detailed logs.
@LouisCapelle
Copy link

same issue here

@hainsdominic
Copy link

Us too

@afloresmorales
Copy link

Hello, were any of you able to fix this issue? I'm getting the same error. Thanks in advance for any updates.

@hainsdominic
Copy link

Hello, were any of you able to fix this issue? I'm getting the same error. Thanks in advance for any updates.

We successfully built widgets/live activities at our startup, here's a blog post about how we achieved it. No need for this library. https://fizl.io/blog/posts/live-activities

@afloresmorales
Copy link

Hello, were any of you able to fix this issue? I'm getting the same error. Thanks in advance for any updates.

We successfully built widgets/live activities at our startup, here's a blog post about how we achieved it. No need for this library. https://fizl.io/blog/posts/live-activities

thank you very much! I'll give it a go

@2winter-dev
Copy link

same issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants