Pendo Mobile SDK

addedAdded The resource center (and its modules) can now be used with guide validation

addedAdded Customers can now use the `annotateUrl` configuration option to provide their own function to determine what “page” a visitor is on. This is particularly useful for customer applications where the url never changes

fixedFixed Tooltips can no longer partially render off the top of the screen (making them unable to be dismissed)

fixedFixed Tooltips now wait to position until all their image blocks have loaded, preventing them from stuttering when rendered with large images

fixedFixed Images for guides created in the Visual Designer now always correctly get display: block, ensuring they don’t create a ~6px gap in their container

fixedFixed Tooltips are better at picking their render direction/offset, and have better handling for mobile-sized screens

fixedFixed Sandbox Modules in the Resource Center now correctly execute csp-compliant javascript

fixedFixed Using pendo.identify()to change an end-user’s language after rendering a guide will now correctly re-fetch that guide’s content in the requested language

fixedFixed Previous Step will now correctly scroll to the previous step for tooltips that are not visible in the viewport

fixedFixed Fixed app latency caused by analytics collection on a pageViewController with a cyclic structure (i.e. the last page takes the user back to the first page and so force).

addedAdded Chat integrations will now persist regardless of whether the Resource Center is open or closed

addedAdded Support for the new “Previous Step” button action in the Visual Designer

addedAdded Support for the new “Launch Guide” button action in the Visual Designer

fixedFixed Customers without body tags can now render guides correctly. Customers who use <frameset> tags, this one’s for you 🙂

fixedFixed The SDK’s recommended flow is to initalize the SDK from the Application object, in order to not lose analytics.

We now found out that some customers want to initialize the SDK from an Activity. While this is not the recommended flow, we enabled this flow and fixed several bugs around this flow.

Note that this means that analytics and guides will not work prior to initializing the SDK.