You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a bad network connection and the widget showed every track as having no ticks except for one which was displayed normally.
Edit: I think I actually was misinterpreting the data when this happened and it isn't an issue. Repurposing this issue for other widget performance related issue:
Newly added widgets can be blank for a while while fetching data from CloudKit, especially with a bad network connection. I can think of two possible solutions:
Only perform a CloudKit fetch if the network connection is strong
In getSnapshot(for:in:completion:), reset the last update time so that new widgets don't try to fetch new data
As far as I can see, the second solution would be much better. The first could potentially also be used alongside it for rare cases where widgets are loaded without a previous timeline entry and without a recent snapshot (maybe on device boot or enabling a home screen).
The text was updated successfully, but these errors were encountered:
I had a bad network connection and the widget showed every track as having no ticks except for one which was displayed normally.Edit: I think I actually was misinterpreting the data when this happened and it isn't an issue. Repurposing this issue for other widget performance related issue:
Newly added widgets can be blank for a while while fetching data from CloudKit, especially with a bad network connection. I can think of two possible solutions:
getSnapshot(for:in:completion:)
, reset the last update time so that new widgets don't try to fetch new dataAs far as I can see, the second solution would be much better. The first could potentially also be used alongside it for rare cases where widgets are loaded without a previous timeline entry and without a recent snapshot (maybe on device boot or enabling a home screen).
The text was updated successfully, but these errors were encountered: