[iOS] Background messages? about watch_connectivity HOT 22 CLOSED

There is a way to send "data" as well that isn't implemented maybe that would do what you need?

from watch_connectivity.

The app shouldn't need to be in the foreground to work

from watch_connectivity.

Unless the phone app is dead then yeah that doesn't work right now

from watch_connectivity.

from watch_connectivity.

I'm going to need more details on exactly what you're trying to do

from watch_connectivity.

from watch_connectivity.

If you need to send data to a dead companion app, then you should probably be using context and not messaging

from watch_connectivity.

from watch_connectivity.

from watch_connectivity.

If you're using context what's the issue? You can read the most recent context with receivedApplicationContext

from watch_connectivity.

from watch_connectivity.

I see. This would require the implementation of the following: https://developer.apple.com/documentation/watchkit/wkwatchconnectivityrefreshbackgroundtask
https://developers.google.com/android/reference/com/google/android/gms/wearable/WearableListenerService

from watch_connectivity.

I've been meaning to implement those for a while, but I haven't gotten around to it

from watch_connectivity.

Ok cool! Might make a PR

from watch_connectivity.

@rodydavis I'm working on a separate plugin to facilitate the calling of flutter code from native code, so if you put any of that logic in the PR for this just know it will most definitely change in the future

from watch_connectivity.

Ok I solved my problem a different way! I had a big json file to send and just chunked it over and saved it with FileManager.

Then I am using the navigation view in swift ui.

something I think that could be useful is docs on how to add the iOS and android watch targets.

from watch_connectivity.

Send file might work! The file is a single JSON file and is about 1.4 MB which exceeds the context limit.

The json file is created from a minimal amount of data from the SQLite DB in the iOS app, but now I only need to sync once and the watch doesnt require the link

from watch_connectivity.

Maybe protobuf could reduce the size of the message

from watch_connectivity.

So it turns out receiving messages from the watch when the phone app is dead doesn't require anything special. It just works. @rodydavis if you listen to the message stream early enough in your app startup, you should be able to get the messages just fine.

from watch_connectivity.

For iOS, Android still requires a lot of work

from watch_connectivity.

Ok sounds good! Thinking about building wear OS directly

from watch_connectivity.

Closing since this was about iOS and that works. We can make a new issue for Android.

from watch_connectivity.