When binding issues occur, e.g. when the app does not start properly, you need to adapt the rules list to first disable, and then gradually re-enable all bindings.
Using the unbind operation will ensure that a matching class, method, or field will not be affected when values are removed during the binding operation. Optionally, the bind operation asks the Shielding Tool to include the specific value in the binding process (which would most likely bind the value regardless).
After shielding, the performance of the application can be impacted at startup. In this case, exclusion options can be defined to reduce the impact of shielding on the application.
The security provided by App Shielding is reduced by excluding classes from the shielding process. The number of bindings must be high enough to ensure security requirements (more than 2,000 push/pull bindings).
Adjust the rules list
In the rules list, you need to specify how App Shielding will modify your app in the context of binding. The rules list is located on the Configuration Page of the OneSpan Mobile Portal.
To modify the rules list
In a web browser, go to the OneSpan Mobile Portal and sign in.
Select the configuration for which you need to adjust the rules list.
Under Settings, add, edit, or remove exclusion rules as needed.
For more information about options and commands to adjust the rules list, see Configuration of Shielding Tool rules.
Additional considerations
If the application terminates unexpectedly during startup, it may be useful to attempt running the application without any form of binding first.
unbind *;If the app works again after this change, you can try to narrow down which class, method, or field is causing the problem. For example, a class initializing might fail due to a
ClassNotFoundExceptionorNullPointerException. The offending class can then be excluded from binding using the following Shielding Tool rule:unbind class com.example.mytestapp.BadClass;