Will do, thanks for the quick response.

Hi - we just launched a new build of our app finally and this issue is still occurring. We thought it was fixed in our test app but now we are seeing it again. Is there any update on this, and is anyone else seeing this issue?Darren Melanson​

Thanks for the update Darren, we will give this a shot. Appreciate it!

Hi Darren,Is this something that can be fixed by enabling WKWebView for our apps? Are there any other workarounds that our team or the AEM Mobile team could use, at least temporarily? This is affecting our production apps and we need to find a fix...Regards,Alex

Hi -We have been struggling with this for several weeks in our apps, and continue to see this issue as of today (10/18). Is there any update on this, and any insight into when a definitive fix will be in place?Thanks,Alex

Decided to go with the Apache basic authentication approach as it is the easiest for our specific requirements. Thanks everyone for your help!

MC Stuff wrote... Hi Alex,    Another option is having Authentication Requirements with value of +/  at http://host:port/system/console/configMgr/org.apache.sling.engine.impl.auth.SlingAuthenticator Thanks,  I like the simplicity of this. When I enable this for a path and attempt to go to that path ...

Hi,Looking for a simple and effective way to password protect one of our staging publisher instance websites that mirrors content from a production instance under a subdomain. Can this be done through AEM somehow? Thanks

Figured it out. Missed the /apps/dam/content migration step in the guide, which was causing the instance to not upgrade properly.

Feike Visser wrote... You might need to recompile/redeploy your code. Did you try to deploy your code to 6.2?  Before starting the upgrade I uninstalled all custom bundles/code. I also tried your suggestion of redeploying my code post-upgrade but core AEM bundles were not updated and retained the 6....