Skip to main content

Mobile Edge always download again when brought to foreground


Phil Seifert
Ultimate Hero (Employee)
Forum|alt.badge.img+23

We encountered an issue with a customer when using the mobile edge iOS application on their iPad and iPhone that whenever the app was brought to the foreground (e.g. closed/reopened or switching between apps) a download executed.

After discussion with the mobile team (thanks @Reid Gilbert !!) the problem appears to be within IIS Manager when the Astea Mobile Edge website has the Enable Static Content Compression enabled.

By turning this off and then IISRESET on the mobile server, the download no longer happens with the exception of the first time bringing the app to the foreground.

 

2 replies

Reid Gilbert
Superhero (Employee)
Forum|alt.badge.img+15
  • Superhero (Employee)
  • 340 replies
  • January 12, 2022

One other tidbit:  We’ve also had some support calls logged for the downloading bar being displayed every time the application is brought to the foreground on the mobile device but the users were pointing at a STAGING link from the Mobile Customizer application.  In this case the system is actually functioning as designed...(this allows you to quickly and easily test the changes that you have made within the mobile customizer application without having to reset the application and re-enter the URL every time...just put the app in the background and bring it to the foreground to trigger the download and you can test the changes quickly.  Once you complete your testing and publish those changes the PRODUCTION link will only have to download the updated code to the mobile device one time).
 

 


Phil Seifert
Ultimate Hero (Employee)
Forum|alt.badge.img+23
  • Author
  • Ultimate Hero (Employee)
  • 1307 replies
  • January 13, 2022

Addendum

We also found the customer had a security tool deployed linked to their Production environment which cached the data and then sent it out.The solution provided above did work in their UAT environment which was not protected by that security tool.

However, when the solution was applied to their Production system, the issue still occurred. Once they disabled the caching in their security tool for the outbound messages, the issue no longer occurred.

The client was trying to get an http 304 response from the server but was unable to do so with this tool in the middle.

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings