K
Kinde6mo ago
TEKIMAX

Branding

Hi I am not able to upload a logo on the branding page, also when I change the design color for the background it does not update when I launch in on expo app. The image is bellow 1 mb.
No description
7 Replies
onderay
onderay6mo ago
Thanks for raising this @Christian Kaman, I will get the team to look into this. Does the file upload spinner keep running with no result? What Kinde SDK are you using?
Chris @ Kinde
Chris @ Kinde6mo ago
Hi @Christian Kaman, I'm looking into the image upload field, which has a few bugs. To get details on your set-up, please send a screenshot of this: https://mybrowserinfo.com/. Also, getting videos is helpful, like taking a screencast of the issue and seeing your browser's DevTools Console for errors. 👍
Your IP Address: 35.196.132.85 - MyBrowserInfo.com (My Browser Info)
MyBrowserInfo.com is the fastest and easiest way to determine your IP address and information about your Web browser.
TEKIMAX
TEKIMAX6mo ago
Yes, the spinner remain I will record a cast
Chris @ Kinde
Chris @ Kinde6mo ago
@Christian Kaman Just on this: "also when I change the design color for the background it does not update when I launch in on expo app", did you hit the Save button at the end of the Branding form as it can get missed (the new UI design features it in the app header to help solve this). Another thing to check is if you applied a Background image in the Page designer, as this will make the background colour not show as the image sits above it.
No description
No description
TEKIMAX
TEKIMAX6mo ago
@Chris @ Kinde I just send you the video
Jeff
Jeff6mo ago
Had the same issue. I enabled custom domain and in the browser developer tools,, I could see a 403 response while the spinner kept doing its thing. Disabled custom domain, retried uploading an image, everything worked, then re-enabled custom domain.
The 403 returned a CORS issue with a custom domain as the pre-flight upload checks have Referrer-Policy set to strict-origin-when-cross-origin Hope this helps.
Chris @ Kinde
Chris @ Kinde6mo ago
Thanks @Jeff that helps a lot - it looks like a CORS issue on resources affecting custom domains - looking into a fix