Common technical pitfalls
Last updated
Was this helpful?
Last updated
Was this helpful?
Over the years of our integrations with multiple businesses, we have come to realize some of the common mistakes developers make during our integration.
A user's location is needed all the time during verification and it is important that this is true before and after a user's address. "Always" for iOS and "Allow all the time" for Android.
A user should not be able to create multiple duplicate addresses for the same location. You can use the OkHi Address Book logic to be able to ensure to not create duplicates for the same location for a user. Address creation should be one at a time, and ideally, controlled by your server so a user is only allowed to create another address if the previous address status comes back as unknown or not at address. Note that a user may have multiple verifications running in parallel on the same device for different locations.
Priming a user simply means you show the user the necessary information before requesting their sensitive location permission and user data. It is important you do this for transparency and also required by the Application stores because of the first reason. Follow this link to .
You should always make sure your user sees an update of their address somewhere in your dashboard when they log into your app as the image below shows.
In order to comply with data privacy requirements, by law we need to (a) notify a user that we are using their location data and (b) provide the option for users to opt out of this data tracking. We do this by notifying users via email, SMS or WhatsApp with a link to their profile on where they can manage these permissions. It can be useful (and is required in cases where we do not send notifications to users) to provide this link in your user profiles for them to manage their address permissions & use.
