Thomas Eizinger
Thomas Eizinger
Looking at the Sentry report, the issue is in fact no file-size but the "latest" symlink.
> Looking at the Sentry report, the issue is in fact no file-size but the "latest" symlink. Actually, this works completely fine if the symlink is not there. Maybe I...
@jamilbk Would appreciate if you could test this on an iOS device.
> Getting this on iOS: > > ``` > Upload preparation for claim 5F5BCE66-F56C-43F9-94FB-55D20D7B48F1 completed with error: Error Domain=NSCocoaErrorDomain Code=260 "The file “latest” couldn’t be opened because there is no...
> > Getting this on iOS: > > ``` > > Upload preparation for claim 5F5BCE66-F56C-43F9-94FB-55D20D7B48F1 completed with error: Error Domain=NSCocoaErrorDomain Code=260 "The file “latest” couldn’t be opened because there...
@jamilbk Could you test on iOS again? I've now disabled the `latest` symlink on iOS as it is unlikely that we are going to use it there anyway.
@jamilbk I've updated this to only use `.zip` on MacOS now. iOS will still use `.aar`. We don't have that many customers on iOS so just getting this out on...
> I actually think the iOS zip export was working - upon further investigation the logs were exported, but the errors shown seem to do with development builds only. >...
This will be much easier with #8263. Currently, we expose each server 1-to-1 to the OS so we don't get to decide, which resolver is used and which one isn't.
@jamilbk Commit history is unfortunately a mess here but overall, I hope the changes aren't too hard to understand. I am planning to do something similar for the Apple client...