What App Center service does this affect?
Build
Describe the bug
Builds failing randomly over the past several days with SQLite error code:6922, 'disk I/O error'. Resubmitting the exact same build over again, or performing another code push, works on the second try.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Valid builds to complete successfully.
Screenshots
error : CoreData: error: (6922) I/O error for database at /Users/vsts/Library/Developer/Xcode/UserData/IB Support/Simulator Devices/08C713DA-B9AF-4028-A13B-1077E4C4B57F/data/tmp/Untitled-v8TjRg50.uicatalog. SQLite error code:6922, 'disk I/O error' [/Users/vsts/agent/2.155.1/work/1/s/...iOS.csproj]
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
Build is for a Xamarin Forms iOS build.
We are also seeing this same issue with our iOS builds. Does anybody have thoughts?
We are also getting the same error in Azure DevoOps
obj/iPhone/Release/actool/cloned-assets/Assets.xcassets : error : CoreData: error: (6922) I/O error for database at /Users/vsts/Library/Developer/Xcode/UserData/IB Support/Simulator Devices/33642807-6BA9-41FB-893D-9FCB619A253A/data/tmp/Untitled-T3cwodDk.uicatalog.
We also have this issue with Xamarin iOS apps that previously built fine
We are also getting the same error in Azure DevOps
obj/iPhone/Release/actool/cloned-assets/Assets.xcassets : error : CoreData: error: (6922) I/O error for database at /Users/vsts/Library/Developer/Xcode/UserData/IB Support/Simulator Devices/33642807-6BA9-41FB-893D-9FCB619A253A/data/tmp/Untitled-T3cwodDk.uicatalog.
Getting the exact same type of error as reported by @Ysquare63 in Azure DevOps - iOS builds that worked fine yesterday are failing consistently today. No code changes.
My build pipeline has two iOS build tasks (A & B) for two different flavors of an app - sometimes A fails and B succeeds, sometimes the other way around, sometimes both fail, never do both succeed.
Very frustrating!
Could you reach out to support via App Center portal, so that we can collect a few more details? Would like to pick couple apps for a deeper look.
@DennisPan I started a conversation in App Center, and the bot responded saying App Center usually responds within a day. Just to be clear, I'm not having this issue through App Center, I'm using Azure DevOps.
@barryculhane Thanks for doing that! I won't be able to collect more information from your Azure DevOps builds, as I don't have access there. There were other customers hitting the same in our support tickets, so I have something to start with, for now.
I assume you are using Hosted Mac images in Azure DevOps? App Center team produces those, so you've still reached out to the right place from that perspective 😄
@DennisPan Yes, we're using the Hosted Mac OS agent. I uploaded the logs ZIP from one of the failed builds, if that helps. Thanks for the speedy response.
Could you reach out to support via App Center portal, so that we can collect a few more details? Would like to pick couple apps for a deeper look.
We're experiencing the same issue with App Center builds. I initiated a conversation in App Center.
@DennisPan The issue appears to have been resolved in Azure DevOps, have successfully queued two different builds without any issues. Thanks for your assistance!
@barryculhane hmmm.... we haven't really found the root cause yet. Let's keep an eye on this given this seems to happen intermittently. Would love to hear from others as well if things start to turn better than before.
Worse actually. Now happening much more often. Last 4 builds failed. Looks like @Ysquare63 reported this issue on the same file as us: "Assets.xcassets".
Here is more detail:
"/Users/vsts/agent/2.155.1/work/1/s/
(_CoreCompileImageAssets target) ->
/Users/vsts/agent/2.155.1/work/1/s/
/Users/vsts/agent/2.155.1/work/1/s/
/Users/vsts/agent/2.155.1/work/1/s/
/Users/vsts/agent/2.155.1/work/1/s/
/Users/vsts/agent/2.155.1/work/1/s/
/Users/vsts/agent/2.155.1/work/1/s/
/Users/vsts/agent/2.155.1/work/1/s/
/Users/vsts/agent/2.155.1/work/1/s/
/Users/vsts/agent/2.155.1/work/1/s/
/Users/vsts/agent/2.155.1/work/1/s/
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets(1218,3): error : actool exited with code 1 [/Users/vsts/agent/2.155.1/work/1/s/
/Users/vsts/agent/2.155.1/work/1/s/
We're also seeing the same error. Last three builds failed 'cause of SQLite error.
Quick update - this is still under investigation. We are testing rolling back recent changes and see if that removes the intermittent failures.
Same problem here in DevOps Pipeline for our Xamarin.iOS Build.
The first build failing with this error was at 31.7.2019, 16:26:31.
obj/iPhone/Debug/actool/cloned-assets/Assets.xcassets : error : CoreData: error: (6922) I/O error for database at /Users/vsts/Library/Developer/Xcode/UserData/IB Support/Simulator Devices/D4160B7E-E418-4671-B6B2-F9015471F3A3/data/tmp/Untitled-Loih3S2i.uicatalog. SQLite error code:6922, 'disk I/O error'
For folks who have been running into this when running builds in App Center, I'd appreciate if you can give this a try:
xcrun simctl erase all in the scriptFor Azure DevOps users, you can add a Shell script task and run the same command.
This fixed a similar issue from other users who installed Xcode 11 beta, which we have on the images.
@DennisPan I have talked to a customer who had this problem (in App Center) and recommended this solution. It seems to work for him.
Great - thanks @jfversluis !
For everyone who have been getting this intermittent failures, if you are still seeing it (with or without the workaround above), please let me know. We've shipped a new image which potentially improves the case here. Would appreciate to know how things are working for everyone, especially if you don't apply the workaround above.
Still failing with same error. Now failing every time. 7 failed builds in a row.
@HarlowBurgess Is that with or without the workaround? Could you also reach out to support so that we can take a deeper look at your builds?
Without workaround. All iOS builds continue to fail. Not sure how to reach out to support. The docs at https://docs.microsoft.com/en-us/appcenter/general/support-center say to go to this GitHub (which I have done) or to "click on the Contact us option in the question menu on the top right of the portal page", only such an option does not exist.
@HarlowBurgess Could you give the workaround a try?
As for support, on the same page you linked:
To get help on any issue you may experience, use the blue chat button at the bottom-right corner of every App Center portal page. Alternatively, click on the Contact us option in the question menu on the top right of the portal page.
The workaround was successful. Thanks!
For folks who have been running into this when running builds in App Center, I'd appreciate if you can give this a try:
- Add post clone script in your repo: https://docs.microsoft.com/en-us/appcenter/build/custom/scripts/#post-clone
- Add
xcrun simctl erase allin the script- Re-save the branch configuration so that the script gets picked up
- Queue a new build
For Azure DevOps users, you can add a Shell script task and run the same command.
This fixed a similar issue from other users who installed Xcode 11 beta, which we have on the images.
The workaround works here too, directly per command line in our DevOps pipeline. Thanks!
For folks who have been running into this when running builds in App Center, I'd appreciate if you can give this a try:
- Add post clone script in your repo: https://docs.microsoft.com/en-us/appcenter/build/custom/scripts/#post-clone
- Add
xcrun simctl erase allin the script- Re-save the branch configuration so that the script gets picked up
- Queue a new build
For Azure DevOps users, you can add a Shell script task and run the same command.
This fixed a similar issue from other users who installed Xcode 11 beta, which we have on the images.
@DennisPan My build failed three times in a row, and then I tried the workaround. It worked.
Thanks for giving this a try and sharing the results everyone! We are rolling out a new image with this, after which you can remove the script in your repository.
Same here - had the build failures then did the workaround and it worked
Work around worked around. Thanks
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: jennablackwell notifications@github.com
Sent: Monday, August 19, 2019 11:39:56 AM
To: microsoft/appcenter appcenter@noreply.github.com
Cc: Ysquare63 yyake@hotmail.com; Mention mention@noreply.github.com
Subject: Re: [microsoft/appcenter] Builds failing randomly with SQLite error (#847)
Same here - had the build failures then did the workaround and it worked
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/appcenter/issues/847?email_source=notifications&email_token=ACS5Z22FZV5ZUBKQWLJJVBLQFLSHZA5CNFSM4IKMU222YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4T426Q#issuecomment-522702202, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACS5Z2Y2W4DZC4XF37ZAAHLQFLSHZANCNFSM4IKMU22Q.
Hello! We've rolled out a new image for our macOS VMs which should resolve this issue. We'd love to hear if building without the workaround is fixed now. Thanks.
When does the new macOS VMs are updated ? it still shows as Date: 2019-08-09 13:12:18 on my Azure DevOps agents.
Azure DevOps agents you provision yourself will not be affected by this change. These images are deployed to the Hosted macOS agents, which are specifically provisioned for App Center.
If you are using the Hosted macOS agents directly through Azure DevOps rather than via App Center, those agents have not been updated yet.
If you have a branch configured for Build on App Center, and were seeing this issue previously, you should be able to run a new build successfully now. Hopefully that makes sense!
This solution worked for me (AppCenter Build)
We haven't seen this for a while, so I'm closing this out. Feel free to reach out if you see more of this.
Appreciate everyone for letting us know you ran into this, giving us the patience and trying the workaround!
Most helpful comment
For folks who have been running into this when running builds in App Center, I'd appreciate if you can give this a try:
xcrun simctl erase allin the scriptFor Azure DevOps users, you can add a Shell script task and run the same command.
This fixed a similar issue from other users who installed Xcode 11 beta, which we have on the images.