06-25-2019, 11:56 AM
Hi,
The only time I heard of such issue was from a user using Curvy with an iOS or Android project. I can't find the said user's post/mail/PM, so I will speak only from memory, but the issue was because the importing process of the assets used in Curvy examples was taking a long time. That was because of the compression options he/she used. The fix was either to simply get rid of the example assets, or to set the project's compression settings to a setting that takes less time.
Does this apply to you?
The only time I heard of such issue was from a user using Curvy with an iOS or Android project. I can't find the said user's post/mail/PM, so I will speak only from memory, but the issue was because the importing process of the assets used in Curvy examples was taking a long time. That was because of the compression options he/she used. The fix was either to simply get rid of the example assets, or to set the project's compression settings to a setting that takes less time.
Does this apply to you?
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.