InvalidApiKeyException on Unit Tests
AlejandroHCruz last edited by
Hi, we're updating our unit tests following the new getting started guide
We're using the new debug API key with v3.1.0 of the SweetBlue & SweetUnitTest dependencies.
The unit tests don't live under our regular package com.company.app but under com.company.bluetooth
What could we do to further debug or fix this issue?
ryanbis last edited by
If you are using a different package name for testing, then you will need a debug key linked to that package name. Email us at email@example.com with the package name, and we'll send you a debug key.