Corrected Japanese localization for iOS offline app

Resolved in Pega Mobile Client version 10.1.1

Illegible text was displayed on controls and labels in offline iOS mobile applications when Japanese localization was selected. Investigation showed the necessary character encoding was missing while building the offline app. This has been resolved by the following Actions:

• Extending the getMimeType function to handle woff extensions.
• Providing an updated method of determining MimeType for iOS 14 and later versions.
• Creating a new function responsible for adding charset encoding to content-type headers if it is needed.

Android devkit handling updated for custom modules

Resolved in Pega Mobile Client version 10.1.1

After creating a module using Mobile Devkit 10.0.0, trying to sync the project with Gradle caused the following error: Failed to resolve: com.pega.mobile:pega-mobile-sdk:8.+.

This has been resolved with an update that forces the use of mobileSdkVersion=10.+ in the devkit.

Improved memory handling for offline mobile apps

Resolved in Pega Mobile Client version 8.8.301

After navigating to a worklist and opening a case, attempting to upload a file to the case triggered an application refresh. This displayed a blank screen and required an application or device restart. This was traced to memory leaks that caused iOS to prematurely end the WebKit process, and was seen most often during memory use surges on earlier versions of iOS when ImagePickerOperation was in progress.

This has been resolved by improving memory usage release in the mobile application, along with added handling for conveniently restarting the application.

Attachments correctly displaying in desktop after sync

Resolved in Pega Mobile Client version 8.8.205

Attachments were not being correctly synced from mobile to desktop when using the offline iOS Mobile app. Attachments were also not displayed in mobile after reset and login. Synchronization was freezing when adding an attachment due to the incorrect handling of operations around the cancel state. If one of the tasks during synchronization was canceled, the sync process was pausing and not finishing because one task remained in the sync queue.

This has been resolved by correcting the operations order. An update is also displayed that restarts the sync if an attachment was added while the sync process was already running.

Dedicated restart application button

Resolved in Pega Mobile Client version 8.8.204

Memory leaks were found, that caused iOS to prematurely end the WebKit process. This was seen most often during memory use surges on earlier versions of iOS when ImagePickerOperation was in progress.

This error required an application restart. A dedicated Restart application button now appears upon this error, making an application restart more convenient to run.

Mobile client custom module improvements

Resolved in Pega Mobile Client version 8.8.203

After creating a custom module and uploading it, configuring the app with the uploaded module caused the build to fail in App Studio. The following error was generated: INFO/MobileBuild: ld: bitcode bundle could not be generated because '/customizer/build/customize/modules/PegaTest3_Device.framework/PegaTest3_Device' was built without full bitcode. This error has been addressed by enabling bitcode in a template project.

The uploadModule task uploaded all modules from the /build directory, not only those specified in the task parameter (—moduleName). This has been resolved by explicitly clearing the /build directory so that only frameworks from the selected module or target are packaged into the ZIP file.

An issue requiring the app/Info.plist file to be copied to app/App-Info.plist has been addressed by updating the AppInfoPlistMerger arguments for the Device target. Additionally, a socket timeout exception related to uploading a large custom module has been resolved by increasing the timeout to 60 seconds.

Corrected scrolling behavior in the mobile modal dialog box

Resolved in Pega Mobile Client version 8.8.102

After you opened a modal dialog box in your mobile application, the pop-up dialog box would scroll up the page and not render as expected. After you closed the dialog box, the background UI would scroll up and be unable to bounce back into position. In addition, you could not hide the action buttons, and the flow action buttons always showed the Cancel and Submit labels that you could not edit. This issue has been resolved with updates to the logic for showing and hiding the top bar.

iOS bottom bar displays properly on scroll

Resolved in Pega Mobile Client version 8.8.100

Scrolling to the bottom of the page in Pega Mobile Client for iOS resulted in the Navigation section intermittently obscuring the Case buttons, preventing you from seeing or performing actions such as Cancel or Submit. The bottom bars were sometimes shown again when the scrolling gesture ended, but the frame of the underlying WebView component did not reappear. This component issue appeared when you built the Pega Mobile Client iOS app with the layout.tabBar.hideBarsOnScroll option turned on, and was traced to the Enable auto hiding bars on scroll checkbox, which did not perform as expected. To resolve this issue, the bottom bar calculation has been updated, and the pan gesture is disabled when the keyboard is visible.

Improved barcode scanning for iPad

Resolved in Pega Mobile Client version 8.7.501

Using the barcode scanning function on an iPad to capture a small barcode on a wristband (0.8cm by 2cm) required manipulating the camera position and distance to the bar. To make this process more efficient, the focus line has been replaced with an icon to improve code recognition speed.

Resolved photo-related performance issues with Field Service app

Resolved in Pega Mobile Client version 8.7.501

The Pega Field Service app was intermittently crashing when you tried to take photos or attach them to cases. Scrolling the list of available photos also had inconsistent performance. This issue was the result of null pointer exceptions in the context, and has been resolved.

Updated https for Google Directions Map on iOS

Resolved in Pega Mobile Client version 8.7.201

The Google Directions Map control was not working properly on iOS devices with the non-HTTPS scheme WebKit. This issue was caused by the pega-https schema that not did provide a needed referer header. In this version, the standard HTTPS protocol replaces pega-https on iOS.