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 have just implemented the default Print Shop experience within my app and when scrolling through the product categories I encounter the following crash which I presume is an assertion failure seeing as it only happens in debug:
This is preventing me from accessing any products from tablet cases and beyond on the list in sandbox environment. Is it possible that this could be fixed? Presuming the faulty image asset just needs replacing/fixing?
Also, when running in live environment, the tablet case image that is causing the crash loads with the below 'Corrupt Image :(' placeholder image.
Is it also possible change this to a placeholder image or a nice failed to load image?
The current failure image seems a bit unprofessional and the average user probably won't understand what 'corrupt image' means, and might distrust the app seeing the word 'corrupt'.
Thanks, Mike.
The text was updated successfully, but these errors were encountered:
I have just implemented the default Print Shop experience within my app and when scrolling through the product categories I encounter the following crash which I presume is an assertion failure seeing as it only happens in debug:
This is preventing me from accessing any products from tablet cases and beyond on the list in sandbox environment. Is it possible that this could be fixed? Presuming the faulty image asset just needs replacing/fixing?
Also, when running in live environment, the tablet case image that is causing the crash loads with the below 'Corrupt Image :(' placeholder image.
Is it also possible change this to a placeholder image or a nice failed to load image?
The current failure image seems a bit unprofessional and the average user probably won't understand what 'corrupt image' means, and might distrust the app seeing the word 'corrupt'.
Thanks, Mike.
The text was updated successfully, but these errors were encountered: