Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
WebCMS Posted October 26 Posted October 26 Settings > Web App > Icons & Images tab is timing out while saving and giving a 504 error page. Tried for 5 times with GIF icons of 512x512, 977 KB and got the exact same timeout and error page. However, the Manifest tab is getting saved fine.
Nathan Explosion Posted October 27 Posted October 27 For the app icon? 7 hours ago, WebCMS said: GIF Pretty sure that's a nope and not supported on iOS and Android. Use a PNG.
WebCMS Posted October 27 Author Posted October 27 (edited) 7 hours ago, Nathan Explosion said: For the app icon? Pretty sure that's a nope and not supported on iOS and Android. Use a PNG. It says on the page - the upload input accepts gif files. I was expecting to see an error message but is branching to an IC error page with 504 Accepted file types: gif, jpeg, jpe, jpg, png, webp Edited October 27 by WebCMS
Nathan Explosion Posted October 27 Posted October 27 That's an image upload field in Invision's software, which accepts several images types. My comment was that GIF is not supported as a PWA app icon on iOS or Android. Keep trying...maybe it will suddenly start working? Or you could use a PNG file. WebCMS 1
WebCMS Posted October 27 Author Posted October 27 1 hour ago, Nathan Explosion said: That's an image upload field in Invision's software, which accepts several images types. My comment was that GIF is not supported as a PWA app icon on iOS or Android. Keep trying...maybe it will suddenly start working? Or you could use a PNG file. It worked with PNG. I was just pointing out the wrong file type listed on the upload input as various upload inputs in IC have different file types listed (eg: Pages > Media have many more file types) and this one has a wrong type listed. Also the page branching to a vague 504 saying the "site is down" when the site is up running fine instead of displaying an error for wrong file type.
Marc Posted October 28 Posted October 28 Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
Recommended Posts