-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fresco already initialized #92
Comments
@MobilefactoryAT We have special fresco setup to support our use case, though this should not pose any conflicts with your use of fresco outside of the GIPHY SDK. We can make this setup method public so that you may call it in advance of presentation of the GIPHY fragment. |
I'm just wondering, when I initialised my Fresco at app startup and later on somewhere in the app your fresco is initialised (eg.: before Giphy bottom sheet is shown) . Does fresco block/use 2x memory and bitmap cache and stuff or just once and your newly set fresco initialisation overrules mine previous initialised cache and ram settings? |
|
Well, I have my own " |
I see, I'll coordinate this with my team and get back to you. |
@MobilefactoryAT |
@ALexanderLonsky thanks `
` |
@MobilefactoryAT please try this version:
You can set it here: Then:
|
@ALexanderLonsky thanks for the fast implementation changes from your side, I'm impressed ;-) `
|
Awesome, looks good! |
we are using Fresco in our app as image cache library anyway and Giphy trys to initialize it twice...
Log appears when Giphy SDK is configured:
Is it possible to disable the secondary initialisation?
The text was updated successfully, but these errors were encountered: