Astea Mobile Update - changed path for downloaded files
Hi,
the latest update for Astea Mobile changed the path for attachments. This is now causing problems for our technicians.
Was this change required from google or why was this changed?
Can someone from Astea please provided latest APK before this update?
Regards
Torsten
Page 1 / 1
Hi Torsten, I just e-mailed you the v3.3.0 native app APK file. The attachment location was changed to use Media Storage per the new Google requirements. What kinds of problems is this causing for your technicians? Are they on Android 10 or 11? Or older versions? Can you replicate the problem? If so, log a ticket and send me the steps to reproduce and I’ll dig into it further, thanks.
Reid
Hi Reid,
thanks a lot for your support. Currently we are using Android 11. Since the Astea-Update there is a conflict with the security software, that we are using. This results in an error message, when some special attachment types tried to be openened from Astea Mobile. For file types which do not have an application installed on mobile in working profile, then it is not able to be opened.
One remark: I just installed the new astea mobile on an mobile without security tool. There we have the same problem. If no application is installed for a file type, then it can not be accessed. This is a real problem. See Screenshot below.
Our FMEs used this functionallity to transfer file types to their laptops and their sharepoint folders.
I will create a ticket in support portal for this.
In wich exact folder can i find the attached files on mobile? I can’t find anyone of them locally on mobile to access from external file manager.
This issue is logged under EU0063680 in our support system...development has completed the changes so that Android 10 and 11 users will be able to locate the uploaded and downloaded attachments in the Downloads/Astea folder. This is now undergoing QA at this time, once it has completed QA I will update this thread with a tentative release date to the Play Store of Version 3.3.2 of the Native App.
This are good news, thanks a lot, Reid!
Update: Android V3.3.2 which contains a fix for this issue has now been submitted to Google and will start rolling out once they approve it (usually within 24-48 hours or so).