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
In my app (Android + iOS) I use content.get() to retrieve data from flamelink.
When I set the populate option to true the call loads for a very long time - by a factor of 10 longer compared to when it's off.
The schema in question is quite simple, but it has three referential fields and one media field.
The network inspector shows low amounts of activity with long idle times in between. At times the SDK seems to load only the media metadate - mostly sequentially and with a request time of ~250ms each:
Is there any way to speed things up here?
Not populating the reference fields would make my app logic quite a bit more complicated, so I'd like to avoid that if possible.
The text was updated successfully, but these errors were encountered:
Also on Android loading times are significantly longer yet again compared to iOS.
Possibly related to this bug in react-native-firebase: invertase/react-native-firebase#5941
We have a react native project and when we run the ios app it takes less than a second to load the content but when we run in on android it takes about 12 seconds to load it.
In my app (Android + iOS) I use
content.get()
to retrieve data from flamelink.When I set the
populate
option totrue
the call loads for a very long time - by a factor of 10 longer compared to when it's off.The schema in question is quite simple, but it has three referential fields and one media field.
The network inspector shows low amounts of activity with long idle times in between. At times the SDK seems to load only the media metadate - mostly sequentially and with a request time of ~250ms each:
Is there any way to speed things up here?
Not populating the reference fields would make my app logic quite a bit more complicated, so I'd like to avoid that if possible.
The text was updated successfully, but these errors were encountered: