When testing noticed that if you added white space we would still be making a call to our APIs with that white space and then fail with a 400. Trimming white space now before comparing the identifiers to see if they are empty or same as what the SDK holds in state. If it's same we avoid the API call and the subsequent failure. Note that there is an exception to this, when setting a profile we will still make the network call but it won't fail since the identifier will not be included. This is because there is no dedup check for set profile calls.
Check List
[ ] Are you changing anything with the public API?
[ ] Have you tested this change on real device?
[ ] Are your changes backwards compatible with previous SDK Versions?
[ ] Have you added unit test coverage for your changes?
[ ] Have you verified that your changes are compatible with all the operating system version this SDK currently supports?
Description
When testing noticed that if you added white space we would still be making a call to our APIs with that white space and then fail with a 400. Trimming white space now before comparing the identifiers to see if they are empty or same as what the SDK holds in state. If it's same we avoid the API call and the subsequent failure. Note that there is an exception to this, when setting a profile we will still make the network call but it won't fail since the identifier will not be included. This is because there is no dedup check for set profile calls.
Check List
Manual Test Plan
1.
Supporting Materials