-
Notifications
You must be signed in to change notification settings - Fork 136
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
Archive failed with return code: 65 #837
Comments
Hi there! Let me clarify a little bit. The archive issue happens if you enable Legacy System or the opposite? Is it related to App Center? Looks like the error is unrelated - is it only reproduced with App Center sdk? If so, could you include the full build log? Thanks. |
Hi @annakocheshkova This issue happening only on Appcenter;
And this one When i enable Build System to "Legacy Build System" happening both Appcenter and Physical computer(Xcode or React Native bundler)
|
Hi, @ibrahimyolbir ! Could you please clarify some details:
|
Hi @AnastasiaKubova Thank you for helping
No its a real project. Yes i can but not here. i can send it as an mail |
Thanks @ibrahimyolbir for share the details. I spent a time for investigate your issue and tried to reproduce it, but it works for me as expected.
And let me know about the result? |
@AnastasiaKubova I tried these steps
But still same. This is my email adress: ibrahimyolbirr@gmail.com if you send a mail to me. I can send you the build logs
|
@ibrahimyolbir thanks for your reply. If you have any private data in logs you can open a ticket in Intercom and share them there (in App Center portal is message button in the right bottom corner). |
@ibrahimyolbir, thanks for sharing logs. I take a look at it, but I don't see any issues related to App Center.
Please let me know about the result. |
@AnastasiaKubova Looks right. As I wrote above, I only encounter this error when building the app in App Center. When I builds it locally, I can build it successfully and I was using an application similar to Appcenter, I did not encounter any problems like this before.
|
@ibrahimyolbir I try to reproduce it, but unfortunately I can't to get this error. Could you please try to reproduce this issue on an empty project? |
@AnastasiaKubova I created an empty project and the installation was completed smoothly. All settings look the same. It will take time to find the problem. If you make a review on what might trigger this error, maybe it might help me. thank you for your help |
@AnastasiaKubova its look like, i don t have these 2 files in the empty project (main.jsbundle and asset) |
@ibrahimyolbir you can try to create these files via command line: Then open the |
Finally! I found the problem. Actually, Xcode creates these 2 files while building. I created them manually as you suggested above before, and this has not been a problem until I created the app in the Appcenter.
|
@ibrahimyolbir thank you for explaining! Can you clarify does this solve your issue? |
Yes Thank you @AnastasiaKubova |
I am glad that the issue is resolved. I'm closing this issue, but feel free to reopen this issue if you have additional questions. |
Hi @AnastasiaKubova - I'm experiencing this issue at the moment. I noticed that it is due to the fact I'm passing However this then causes my Test Flight app to crash on launch. I was able to come to this solution because I ran my scheme in release on my own device and it produced an error 'No jsbundle', when the main.jsbundle file was removed from Copy Bundle Resource however when added again it worked as expected... Would you be able to help me? Thanks a lot! |
Hi there @maxckelly! So you created and passed these files manually similar to @ibrahimyolbir before, right? |
Hi @annakocheshkova - Thanks for the quick response. Here is everything I've done. React - "react-native": "0.62.2"
I encountered a build issue "no URL bundle present" when running locally both in debug and in release. However I found a solution for that here: https://www.youtube.com/watch?v=eCs2GsWNkoo which works great. I added the However My issue is when I build the app on App Center with the
Knowing this I then went back into xCode and removed I believe the cause of the crash on Test Flight is due to no I also attempted to build with legacy build system however this then resulted in the below error with App Center:
Any ideas on what I could do? Thanks again for all your help! |
I don't think our SDK does anything specific related to jsbundle, but this feels to me like a question more related to the App Center build system. |
Sure, opened up a ticket. Hopefully can get to the bottom of it. Thank you for your help @annakocheshkova greatly appreciated. |
@maxckelly did you have any luck finding the cause of this? I'm experiencing the same issue |
Unfortunately my solution was to revert back to a stable branch and drop my schemes down to one release and debug. I'm interested though in finding the cause of this as I spent 4 days on it and still couldn't get to the bottom of it. So please let me know if I can help. I had three schemes
Part of my solution as well was to cut this down to one scheme
The reason I say this is that I had a feeling I may have duplicated the wrong scheme (duplicated a debug scheme but running it at release etc...) this then would've caused issues with code push. Do you have a similar setup? It's a very frustrating build issue so if you need anymore help or want to share files etc let me know. |
@maxckelly I had the exact same problem as yours and managed to fix it.
Xcode build fine locally, run fine on device. |
@origamih what do you mean by "I added resources and bundle file to ios" - you added it in xcode some way or how? I fullfill other conditions but issue still occurs. |
@kpietrzak-web run |
can you explain more? |
Seems like a re-occurring issue. I am experiencing it only in AppCenter. Building locally seems to work real fine. |
Mine happened after adding 🗡️ OneSignal |
I've added the main.jsbundle to git to be part of the version control and the appcenter build has passed 💪🏻. However I think this is not what was intended. |
Hi @chenop Glad you found a solution. I think your concern is valid and I wouldn't recommend storing |
Hello Guy's I got below issue in app-center and tried all this things but didn't work , any solution on this?? ** ARCHIVE FAILED ** The following build commands failed: |
Hi @sanjib-tatva thank you for reaching out to us! This issue doesn't look like it is related to the AppCenter SDK. Could you try to remove the AppCenter SDK from your project and confirm that it archives after that? |
Hello @DmitriyKirakosyan Thanks for the response. I used below version of app-center "appcenter": "4.3.0", |
Hi, @sanjib-tatva ! |
Hello, @AnastasiaKubova! In xcode it's working and successfully generating the archive build but in appcenter only I got this issue ** ARCHIVE FAILED ** The following build commands failed: |
@sanjib-tatva , thanks for clarifying, if this issue happens only on the App Center portal then this is not an SDK issue. Please open a support ticket on the App Center portal. |
@AnastasiaKubova , Thanks for quick response. |
Hi, we are having the exact issue in MS App center for iOS build. The build failes intermittently only with below error: Leading up to is below error XCode 13.2.1 ios Native App. Can you share issue resolution for the support ticket mentioned above? |
Hi @balukadiyala , please contact support on this question. |
For me the reason was just modified provision profile, because I've enabled some other features through appstoreconnect. I just needed to download the new one and upload it to appcenter. |
For people who are running into this issue with Xcode 14 and React-Native 0.70.1. I've modified the post_install do |installer|
# Run the React-Native post install
react_native_post_install(installer, :mac_catalyst_enabled => false)
__apply_Xcode_12_5_M1_post_install_workaround(installer)
# Get the development team id from the main project
dev_team_id = ""
project = installer.aggregate_targets[0].user_project
project.targets.each do |target|
target.build_configurations.each do |config|
if dev_team_id.empty? and !config.build_settings['DEVELOPMENT_TEAM'].nil?
dev_team_id = config.build_settings['DEVELOPMENT_TEAM']
end
end
end
# Reconfigure the pods, update deployment target and signing settings
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
if target.respond_to?(:product_type) and target.product_type == 'com.apple.product-type.bundle'
config.build_settings['DEVELOPMENT_TEAM'] = dev_team_id
config.build_settings['CODE_SIGN_IDENTITY'] = 'Apple Distribution';
config.build_settings['CODE_SIGN_STYLE'] = 'Manual';
end if
config.build_settings.delete 'IPHONEOS_DEPLOYMENT_TARGET'
end
end
end It will automatically fix the signing settings of some of the Pod projects. It will also reset the deployment targets of those projects (fixes some warnings, but isn't necessary to fix the archive failed error). |
Hello, I encountered a problem while building the appcenter, but it can run normally locally. What is the reason for this? The following build commands failed: ##[warning]Deleting provisioning profile: /Users/runner/Library/MobileDevice/Provisioning Profiles/8ca8e920-aefb-4bd9-a879-175eb82c829a.mobileprovision I used some environment variables on the appcenter to build the project, and I'm not sure if this is related to it |
Hi @shaozhihui , It seems you're attempting to build your project on App Center. For assistance with that, please contact our support team directly; they'll be able to assist you promptly. |
Description
** ARCHIVE FAILED **
The error appears in these 2 files main.jsbundle and assets. Works fine on emulator and physical device
The following build commands failed:
When i try enable to "Legacy Build System"
Please list the steps used to reproduce your issue.I no longer receive this error. But I get an error like
clang: error: linker command failed with exit code 1 (use -v to see invocation)`
Details
react-native info
System:
OS: macOS 10.15.3
CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Memory: 59.17 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 14.2.0 - /usr/local/bin/node
Yarn: Not Found
npm: 6.14.4 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
Android SDK: Not Found
IDEs:
Android Studio: 3.6 AI-192.7142.36.36.6241897
Xcode: 11.4.1/11E503a - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_242 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: ^16.13.1 => 16.13.1
react-native: ^0.62.2 => 0.62.2
npmGlobalPackages:
react-native: Not Found
pod --version
pod --version. 1.9.1
[MSAppCenter setLogLevel: MSLogLevelVerbose];
before your call to[AppCenterReactNative register];
(or any other SDK registration). For Android, useAppCenter.setLogLevel(android.util.Log.VERBOSE);
before yourSoLoader.init
call (you will need toimport com.microsoft.appcenter.AppCenter;
). Include the logs here:The text was updated successfully, but these errors were encountered: