Hardcode ip for provisioning, fix client used with apikey #385
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates to use the ip
10.42.0.1
instead of a hostnameviam.setup
during provisioning. Usingviam.setup
while using cellular (but connected to the hotspot) on iOS does not work and the requests fail.Also,
Testing in my example project, I couldn't get the init w/ api key to function (for provisioning): viamrobotics/viam_flutter_bluetooth_provisioning_widget#2
I think the host
provisioning.viam
in this init for theProvisioningClient
is outdated / doesn't match how it's setup when using an access token (usesviam.setup
). Plus we want to use an ip now here as well