I am looking for an API which can make the whole app unmasked. What I currently see is a view or a view controller (screen) can be unmasked.
Also, I saw below in the documentation that SDK do not support unmasking of UIWindow.
Could someone please guide me on how to unmask the app overall. The documentation is not really helpful. Thank you
0
Comments
1 comment
Lindsay Zubrickas
Hey @Zeeshan! Thank you for your question! 😊
I see you’ve reached out to our support team and they’re helping you out! I’d also like to share the answer here as well, so that other folks can reference this should they have a similar question. 😎
There is no way to unmask an entire app. The reason behind this is because universal unmasking can lead to sensitive data being captured when changes are made to an app. For instance, if the name of an element changes or a new element is added that could contain sensitive data, these elements wouldn't be masked by default any more. We pride ourselves in leading the industry by taking a privacy first approach to capturing data and being conscious of the sensitive data end users' devices may contain. That’s why Private by Default is required for all native mobile capture.
While we don't provide a way to entirely unmask your mobile sessions, you can unmask parent container elements to unmask all of the child elements (which can be helpful to unmask many elements with a single unmasking rule). You can unmask your mobile app using either the code-first approach or by using the in-app data capture rules in Settings.
You’re definitely in good hands with our support team, but please don’t hesitate to reach out should you have any other thoughts or questions!
Comments
1 comment
Hey @Zeeshan! Thank you for your question! 😊
I see you’ve reached out to our support team and they’re helping you out! I’d also like to share the answer here as well, so that other folks can reference this should they have a similar question. 😎
There is no way to unmask an entire app. The reason behind this is because universal unmasking can lead to sensitive data being captured when changes are made to an app. For instance, if the name of an element changes or a new element is added that could contain sensitive data, these elements wouldn't be masked by default any more. We pride ourselves in leading the industry by taking a privacy first approach to capturing data and being conscious of the sensitive data end users' devices may contain. That’s why Private by Default is required for all native mobile capture.
While we don't provide a way to entirely unmask your mobile sessions, you can unmask parent container elements to unmask all of the child elements (which can be helpful to unmask many elements with a single unmasking rule). You can unmask your mobile app using either the code-first approach or by using the in-app data capture rules in Settings.
You’re definitely in good hands with our support team, but please don’t hesitate to reach out should you have any other thoughts or questions!
Please sign in to leave a comment.