Failed to backup assets. Retrying...

[torn sonnet]

Decent chance it has to do with me removing typesense from my docker compose by accident, and readding it after.
How can I fix it? It has been throwing this error sometimes during today.

This is the only error in my android app log

"Catch all error: Bad state: No element - Bad state: No element"

#0 ListBase.firstWhere (dart:collection/list.dart:132)
#1 Store._onChangeListener (package:immich_mobile/shared/models/store.dart:76)
#2 _RootZone.runUnaryGuarded (dart:async/zone.dart:1594)
#3 _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339)
#4 _BufferingStreamSubscription._add (dart:async/stream_impl.dart:271)
#5 _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:784)
#6 _StreamController._add (dart:async/stream_controller.dart:658)
#7 _StreamController.add (dart:async/stream_controller.dart:606)
#8 Stream.asyncMap.<anonymous closure>.add (dart:async/stream.dart:788)
<asynchronous suspension>
#9 Stream.asyncMap.<anonymous closure>.add (dart:async/stream.dart:787)
<asynchronous suspension>

[untold zealot]

:wave: Hey @torn sonnet,

Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich .

References

• Container Logs: docker compose logs docs
• Container Status: docker compose ps docs
• Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
• Typesense: You can't fix this. Just wait until we get rid of it. Sorry.

Checklist

1. :blue_square: I have verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: I have read applicable release notes.
3. :blue_square: I have reviewed the FAQs for known issues.
4. :blue_square: I have reviewed Github for known issues.
5. :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the /upload command.
7. :blue_square: I have tried an incognito window, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

@torn sonnet uploaded

[noble shell]

Any error in your server log?

[torn sonnet]

In which container?

I may have too many containers and have to prune some, woops

[noble shell]

immich-server

[torn sonnet]

Nothing noppes

I can't seem to force the error to occur

Everything seems to be backed up?

Okay, I took a single random screenshot and immich is now trying to back it up, but its taking a whilee

Its stuck at like 1 fifth progress on the android notif

[raven wadi]

I made the same mistake. Thanks for letting me know I wasn't the only one.
I tried to repair but had too many issues.

I just left my mistake in place so it'll be correct when the time comes. 😉 My only problem is I can't use search.

I'm stupid for doing this, but the way the docs were written was pretty unusual and out of the blue.

[torn sonnet]

I mean

It says "next release" in big huge bold letters xD

I believe this is more user error than anything else

[raven wadi]

Announcement (Breaking changes next release - across multiple "next" versions. Like I said my mistake, but it's badly written.

[leaden knot]

What would be the better way to write this? I think lots of people are confused so it is our fault

[raven wadi]

My mistake was I was a few versions behind - I scroll through past 1.90.1 and see a breaking change next release (gloss over the 1.91.0 in the text), then I scroll to the top version which also has the same message. It was the "next release" that caught me out and having instructions to complete the task in multiple versions.

I always deploy without much thought as I want to try your new features so went for it. I also probably have mild dyslexia which I'm sure doesn't help.

I guess if I was doing your docs, I would have followed your method of announcing the v1.87.0 next version breaking change - with no instructions and a supporting post in discussion. Then in v1.88.0 when the breaking change was present - provide instructions.

[leaden knot]

Good idea, thank you for your suggestion

[torn sonnet]

In my case I just glanced and someone had told me there would be breaking changes next release, and I thought this was it so I didn't read properly.

I agree with the suggestion, don't provide instructions! I didn't even think about that.

[torn sonnet]

Solved! I misdiagnosed the issue, it was cloudflare 200MB limit.