Skip to content

Hardcode ip for provisioning, fix client used with apikey #385

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 15, 2025

Conversation

kevin49999
Copy link
Member

@kevin49999 kevin49999 commented May 14, 2025

Updates to use the ip 10.42.0.1 instead of a hostname viam.setup during provisioning. Using viam.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 the ProvisioningClient is outdated / doesn't match how it's setup when using an access token (uses viam.setup). Plus we want to use an ip now here as well

@@ -7,8 +7,6 @@ enum NetworkType { wifi, wired }

/// {@category Viam SDK}
/// gRPC client for connecting to Viam's Provisioning Service
///
/// All calls must be authenticated.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is the one client where this doesn't apply

@kevin49999 kevin49999 requested a review from ale7714 May 14, 2025 01:14
@kevin49999 kevin49999 requested a review from clintpurser May 15, 2025 14:45
@kevin49999 kevin49999 changed the title Update ProvisioningClient init when used with api key Hardcode ip for provisioning, fix client used with apikey May 15, 2025
@kevin49999 kevin49999 merged commit 92405d0 into main May 15, 2025
4 checks passed
@kevin49999 kevin49999 deleted the update-provisioning-init branch May 15, 2025 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants