feat(mobile): Background app refresh status

[martyfuhry]

Adds a message that App Refresh is currently disabled and a settings button to navigate to app settings.

Unfortunately, the Go To Settings takes you to Settings > Immich instead of Settings > General > Background App Refresh.

• There is not a safe way to navigate to the latter. Maybe the message should say that's where they need to go?
• If Background App Refresh is on globally, but off for Immich, the system still reports that it's "available". This will be obvious for folks with 0 processes queued, though.
• App Refresh tasks can now be scheduled even when connected power is required; they will check to see if they have power and if so, run, otherwise immediately complete.
• Fixes an issue where turning off and on background app refresh would clear all Immich tasks until a full app restart. Now you just need to reopen the Immich app to bring it back to foreground to reschedule the background tasks.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated
immich	⬜️ Ignored (Inspect)			Feb 23, 2023 at 5:54PM (UTC)

[alextran1502]

I think we should use ref.watch here? is there any reason you are choosing to use ref.read?

[martyfuhry]

Not really sure. I guess watch will update this provider when it changes? This only barely depends on the backgroundServiceProvider at all; it just had all the method channel communication functions in it, so I piggybacked there.

I'm still not super familiar with RiverPod and there's likely something I'm not doing correct here. But I made the change and it still seems happily working here.

[alextran1502]

Riverpod suggests using ref.watch as much as possible I believe. Only using ref.read in button pressing context.

Here is some good info
https://riverpod.dev/docs/concepts/reading#using-ref-to-interact-with-providers

[martyfuhry]

Thanks! I gave it a read and it's becoming clearer to me.

In any event, I changed it to ref.watch and looked through the code to find other ref.read statements. In this case, the other ref.read statements are justified as they are just one-off refreshes (app resume and page load).

[alextran1502]

If you are using StateNotifier I believe you have to use StateNotifierProvider here instead of StateProvider. Is using StateProvider do what you are expecting?

[martyfuhry]

Forgot to say I resolved this.