It is expected that Apple will start rolling out the iOS 15 Operating System within the next 2-3 weeks, theiOS 15 Operating System is NOT YET CERTIFIED for use.Mobile technicians SHOULD NOT UPGRADE to this operating system version at this time, please instruct your mobile technicians to hold off on upgrading until this version has been certified for use with Astea Mobile.I will update this thread once the official release has completed QA testing.
NOTE: This issue applies to the Mobile Universal application ONLY (not Mobile Edge) and this issue only occurs on Android devices (not iOS devices).Recent Google Chrome updates are causing an issue with the horizontal ‘carousel’ scrolling functionality in the Mobile Universal application. This prevents users from scrolling all the way to the left to access all of the tabs in the Work List module. Users will need to click on the Uninstall updates to roll back the Google Chrome update to resolve the issue (and hopefully future updates to Chrome will correct the problem). Other workarounds you can use would be to run the Mobile Universal application through a different browser app (one not built on the same Chromium Engine that Google Chrome and Edge run on) such as Bing. If you are still running on the V11 or V12 Mobile Universal platform this application is end-of-life and on Restricted Support so please reach out to your Project Manager to get started on your upgrade to the latest s
There is a known issue for users that are running V3.3.0 of the Astea Mobile Native application on Android Devices, this issue does NOT APPLY to iOS Devices: Users are getting notifications that the Baidu push notification service is running on their devices (even though they are currently using Google Push Notifications and nothing related to Baidu Maps or Notifications is installed or configured on the mobile device). These notifications can be ignored. This issue happens after the device is powered off and then back on again, technicians can use a temporary workaround in the meantime if they want (but once the device restarts it will happen again):Go to Settings and click on Apps.Scroll down through the list and click on Astea Mobile.Click on Force Stop.Now they can launch Astea Mobile again and the notification will not appear (until the next power cycle).We are actively working on the fix for this issue and are targeting it for inclusion in the next V3.3.1 release. I will updat
iOS 14.7 Operating System is NOT YET CERTIFIED.Mobile technicians SHOULD NOT UPGRADE to this operating system version at this time, please instruct your mobile technicians to hold off on upgrading until this version has been certified for use with Astea Mobile.
iOS 14.8 Operating System is NOT YET CERTIFIED.Mobile technicians SHOULD NOT UPGRADE to this operating system version at this time, please instruct your mobile technicians to hold off on upgrading until this version has been certified for use with Astea Mobile. I will update this thread once it has been certified for use by our QA department.
Apple recently started rolling out the iOS 17 Operating System...please note that theiOS 17 Operating System is NOT YET CERTIFIED for use.Mobile technicians SHOULD NOT UPGRADE to this operating system version at this time, please instruct your mobile technicians to hold off on upgrading until this version has been certified for use with Astea Mobile.I will update this thread once this update has completed the certification process.Thanks,Reid
A new version V3.3.3 of the iOS Astea Mobile native application is currently undergoing QA at this time. This version includes upgrades to the iOS SDK’s with the latest security updates and a plug in for Crashlytics which will give us the ability to capture more detailed information on the support side when needed (there are no functional changes, enhancements or features included that would impact your technicians directly). The minimum iOS operating system version required for this release is iOS 12.4. I’ll update this thread once we have a tentative rollout date scheduled.
A new version V3.3.4 of the Android Astea Mobile native application is currently undergoing QA at this time. This version includes the following updates:New Splash Screen (The logo will appear smaller when the application is launched).Upgraded to Android SDK 32 for Android 12+ support (NOTE: The Android 13 operating system is still undergoing certification at this time).GPS Upgrades to fix some intermittent crash errors on Android 11+ that were reported via the Crashlytics logs.I’ll update this thread once we have a tentative rollout date scheduled.
A security vulnerability has been reported on older versions of .NET (6.0.20 and lower), details on that are as follows:The vulnerability involves Microsoft's .NET, which are frequent attack vectors for malicious cyber actors. The nature of the exploit in this attack is unclear, but Windows has acknowledged the existence of a proof-of-concept (PoC) about this vulnerability. Exploiting this vulnerability allows malicious attackers to perform denial-of-service attacks on the system.If you are running the Mobile Edge application on version 15.4.9.0 or lower then your environment is not running on .NET 6.0.21 which contains the fix for this vulnerability. Versions 15.4.10.0 and higher of Mobile Edge include the support for .NET 6.0.21 and will automatically upgrade the environment as part of the installation process so if you are not running on V15.4.10.0 or higher at this time please reach out to the Support Department or your Project Manager to escalate the upgrade effort.Thanks,Reid
There is a known issue with the Astea Mobile application crashing on the login screen after an uninstall/reinstall for users that are running version 3.3 of the Astea Mobile Native App on iOS Devices, this issue does NOT APPLY to Android Devices. When the users log into the mobile application we have logic that tries to communicate with the Baidu servers in China (and this currently happens whether you are configured to use Baidu Notifications or Google Notifications), if the device cannot connect to Baidu within a certain period of time an error is thrown which is not handled properly which causes the application to crash. The workaround in the meantime is to get the mobile device connected to a network (i.e. WiFi or Cellular) which allows access to Baidu services during the login/install process. There are reports that the AT&T Cellular network is randomly blocking access to certain websites in China so switching to WiFi temporarily may be required in those situations.We have
A new version V3.3.7 of the Astea Mobile Native Application is currently undergoing testing at this time, updates are included for the following items:Application crashes on Android 12+ devicesI’ll update the thread with a tentative ETA for the rollout once it has completed QA.Thanks,Reid
iOS 14.7.1 Operating System is NOT YET CERTIFIED.Mobile technicians SHOULD NOT UPGRADE to this operating system version at this time, please instruct your mobile technicians to hold off on upgrading until this version has been certified for use with Astea Mobile.
There is a known issue with the GPS tracking for users that are running version 3.3 of the Astea Mobile Native App on Android Devices, this issue does NOT APPLY to iOS Devices. If MOE -10131 is set to a value of 1 the mobile device does not capture GPS coordinates, we are currently working on the fix for this issue and will include it in the upcoming 3.3.1 Native App release (the release date is still yet to be determined). As a temporary workaround in the meantime you can change MOE -10131 to a value of 3, have your impacted technicians log out of the application and log back in again (this will download the updated MOE value to their mobile devices). Then have them go to the Communication Diagnostics module and enable the “GPS Tracking” toggle on this screen, this will ensure that their GPS coordinates are captured in the meantime. MOE -10131 Location Tracking: (1: Hidden but Location Tracking Enabled, 2: Hidden but Location Tracking Disabled, 3: Visible and Tech can edit, 4: Visi
An issue has been reported where the Astea Mobile application running on certain (not all) iPad devices is showing the Cordova icon instead of the Astea Mobile icon. Development is aware of the issue and is currently working on a fix (which will be rolled out in the V3.3.4 release). incorrect icon looks like this
A new version V3.3.5 of the Astea Mobile Native Application is currently undergoing testing at this time, updates are included for the following items:Fix crash that happens to some devices when selecting photos from library Fix compression quality to respect MOE -10294 value when selecting photos from libraryI’ll update the thread with a tentative ETA for the rollout once it has completed QA.Thanks,Reid
The Astea Mobile application has been temporarily removed from the Google Play Store while we make updates to our Privacy Policy information (that part was completed yesterday so we are just waiting on final approval from Google at this point in time). As a temporary workaround users can download the App by entering the following link into a Chrome or Safari browser window and clicking on the Android Client link:https://qac.astea.cloud/asteamobileedge/install.htmlOr they can enter this URL to download it directly:https://qac.astea.cloud/asteamobileedge/client/android/AsteaMobile.apkAfter the download is complete click on Open to complete the installation process.
We recently had an issue reported in a customers UAT environment where the users were logging into the Mobile Edge application via a customized mobile URL (created via the Mobile Customizer application) and they were getting a white screen on Android devices, iOS devices and on Google Chrome. Adding to the mystery was the fact that we were unable to recreate the issue on their PROD environment which had the same mobile build and customization installed...We build the mobile customization map information (i.e. whether it’s using Baidu Maps or Google Maps along with the associated key information) dynamically and that setting is pulled from the GIS entry associated with the profile in the Configuration Editor. To fix it we had to launch the Configuration Editor on this environment, click on the Profile and then scroll down and ENABLE the GIS section below (this explains why we couldn’t replicate the issue in PROD because that environment already had GIS configured). Hit the save butto
We have a new issue reported with the integration link between Mobile Edge and Help Lightning: when the mobile technician clicks on the link in Mobile Edge it no longer opens the Help Lightning application directly...the user is taken to the Google Play Store instead of going directly into the app. From there they need to click on the Open icon to get into the Help Lightning application which they didn’t need to do in previous versions (and shouldn’t NEED to do). This issue ONLY happens on Android devices (it works properly on iOS devices at this time). This has been routed to Help Lightning’s development team and they will let us know once it has been resolved (and then I’ll update everyone on this thread).
Google recently started rolling out the Android 14 Operating System...please note that theAndroid 14 Operating System is NOT YET CERTIFIED for use.Mobile technicians SHOULD NOT UPGRADE to this operating system version at this time, please instruct your mobile technicians to hold off on upgrading until this version has been certified for use with Astea Mobile.I will update this thread once this update has completed the certification process.Thanks,Reid
A new version V3.3.6 of the Astea Mobile Native Application is currently undergoing testing at this time, updates are included for the following items:No issues were addressed in this release, the only change is: Remove Firebase Crashlytics to adhere to Google Play Developer Program policies.I’ll update the thread with a tentative ETA for the rollout once it has completed QA.Thanks,Reid
There was a change in Google Chrome 110 which was recently released which impacts the Mobile application when run from HTTP URLs (this should not be the case for PROD environments but you may have development/support/QA/staging environments that are configured in this manner). This issue will only affect users running the application in Google Chrome (it will not impact techs running on the iOS or Android Native applications). When they try to browse the http:\\YourServerGoesHere\AsteaMobileEdge\ URL on a Chrome browser the screen will display a white screen, if you open up the Developer Tools and look at the Console Log you will see an error that says the following:Access to the WebDatabase API is denied in non-secure contexts.The solution here is to update the Registry Settings on the PC with two new REG_DWORD values (and then close and re-launch Chrome afterwards). Details can be found on the following Google links:https://chromeenterprise.google/policies/?policy=WebSQLAccesshttp
A new version V3.3.8 of the Astea Mobile Native Application is currently undergoing testing at this time, updates are included for the following items:Fix for the Image Picker plugin, enabling access to the Gallery/Album on Android 13+ devices. Fix for the Notification Plugin, ensuring correct setup of notification permissions on Android 13+ devices. Upgrade of the Cordova Android Platform to version 12.0.1 to address an application crash issue when calling one of the plugins.I’ll update the thread with a tentative ETA for the rollout once it has completed QA.Thanks,Reid
The iOS 14.5.1 Operating System is now certified for use with the Mobile Universal and Mobile Edge applications.
The iOS 14.6 Operating System is now certified for use with the Mobile Universal and Mobile Edge applications.
A new version 3.3 Native Application will be rolled out to the Play Store shortly, updates are included for the following items: Display "Service URL" in settings of AsteaMobileEdgeGPS support for Android 11Baidu notifications supportFix audio attachment uploadsNew policy link available on server URL screen
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
