Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cannot access iOS build artifacts
See original GitHub issueipas get successfully built on http://tabrisjs.com , but when trying to download them, following XML is served instead:
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>...</RequestId>
<HostId>
...
</HostId>
</Error>
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:40 (3 by maintainers)
Top Results From Across the Web
An internal error occurred while this artifact was being saved.
Builds worked fine until yesterday, and now we're getting this error about the logs. Seems the build goes fine, just no logs artifacts...
Read more >Problems after upgrading to Xcode 10: Build input file cannot ...
Go in the project-navigator, select your project · Select Build Phases tab · In Compile Sources section, check for the file(s) that Xcode...
Read more >iOS Build Troubleshooting - Visual Studio App Center
To fix this error, open your project's Build configuration and click Save. App Center will automatically choose the workspace correctly for ...
Read more >Files exists but can't be used to build artifacts. (#15530) - GitLab
I want to create build artifacts, but Gitlab CI keeps telling me no matching files, although I explicitly check if the files exists....
Read more >Artifact Publishing does not copy everything - Blocks Xcode ...
Quick fix to your problem would be to tar your app directory to preserve all attributes, use this tar as a artifact and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Among other things I can see is that your app revision changed between these two builds. The working build is
808f887a3a3cfe9053e8c93697fdda0fa3e1dc6fthe broken build8924b5ce112a00aff8dc4d02c0e8317202d6e031. Could you create a branch pointing to your old revision and build this?@bFlood Thanks for keeping us in the loop. I’m glad we finally figured out what the problem was.
I’ll close this issue and shut down the snapshot environment on Monday.