Skip to content
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

Problems with Polar 360 onboarding! #550

Closed
9 tasks
abbjetmus opened this issue Feb 5, 2025 · 14 comments
Closed
9 tasks

Problems with Polar 360 onboarding! #550

abbjetmus opened this issue Feb 5, 2025 · 14 comments
Labels
question Further information is requested

Comments

@abbjetmus
Copy link

abbjetmus commented Feb 5, 2025

Platform your question concerns:

  • Android
  • iOS
  • Other
  • Platform is not relevant for this question

Device:

  • Polar OH1
  • Polar Verity Sense
  • Polar H10
  • Polar H9
  • [ X] Polar 360
  • Device is not relevant for this question

Description:

Hi Guys!
We are trying to provide a seamless onboarding for our customers using Polar 360, but unfortunetly the new flow on Polar 360 with FTU are troublesome.

Polar 360 allows us to be connected to the sensor - status = connected without having completed PAIRING or FTU, but we cannot start measuring before doing those two things.
We also don't know if they succeeded because we can't ask the sensor about if FTU is done or if PAIRING is done. Our customers have problem with this since we want to start measuring directly. But they end up with one of these steps failing and our app don't know about it.

If they have succeeded with both and do a factory reset later I have a variable in shared preferences indicating if FTU is done which will not be valid anymore.

Can we ask the sensor if PAIRING is done or FTU is done?

It would have been nice if one could decide to skip FTU completely.

With Polar Verity Sense these issues was not present since it had an easier onboarding.

@abbjetmus abbjetmus added the question Further information is requested label Feb 5, 2025
@vedantgurav
Copy link

vedantgurav commented Feb 5, 2025

Hey. @abbjetmus, we have had similar issues with the pairing flow. On iOS we are handling these by looking for the following errors.

We now look out for the PolarErrors.notificationNotEnabled error which means pairing has failed.

Missing FTU usually causes the PmdResponseCode.errorInvalidState error, although this is not exclusive.

Additionally to handle cases where the Device is factory reset, we check here and here for the CoreBluetooth errors .peerRemovedPairingInformation and .encryptionTimedOut respectively. In this case we just prompt the user to manually forget the P360 from bluetooth settings. If we get encryptonTimedOut, a P360 reset is also required. After this the app can pair once more.

@abbjetmus
Copy link
Author

abbjetmus commented Feb 5, 2025

Thanks for the response @vedantgurav, will check your suggestions. Looking forward for a response from Polar as well?

@rkangast
Copy link
Contributor

FLOW-62499

@palmqvisti
Copy link
Contributor

Hello from Polar! We will add a "isFtuDone" kind of method to check for the state of FTU. Hope that helps in this issue.

@abbjetmus
Copy link
Author

That would be nice also if there was a way to know if the sensor already has a pairing and to which device would be helpful.

@rkangast
Copy link
Contributor

Hi,

Unfortunately that cannot be done. Once Polar 360 has been paired to a device it will no longer pair to any another device that would possible allow checking the existing pairing data.

@abbjetmus
Copy link
Author

@rkangast we are on boarding new users next week is it possible to get a patch this week with isFtuDone?

@rkangast
Copy link
Contributor

@abbjetmus This should be doable. I will start implementing and hopefully we get the new api through our process by the end of this week.

@rkangast
Copy link
Contributor

Hello @abbjetmus,

isFtuDone method will be released today in the next SDK release (5.14.0).

@abbjetmus
Copy link
Author

abbjetmus commented Feb 14, 2025

Thank you @rkangast, you have the best support!

@abbjetmus
Copy link
Author

abbjetmus commented Feb 16, 2025

@rkangast @jimmyzumthurm version 5.14.0 build didn't complete in you CD. I can't access it could you guys rebuild or fix the deployment?

pod search PolarBleSdk

-> PolarBleSdk (5.13.0)
SDK for Polar sensors
pod 'PolarBleSdk', '~> 5.13.0'

@abbjetmus abbjetmus reopened this Feb 16, 2025
@rkangast
Copy link
Contributor

Hello @abbjetmus,

Deployment of version 5.14.0 has been now fixed. Sorry for the inconvenience!

@abbjetmus abbjetmus reopened this Feb 17, 2025
@abbjetmus
Copy link
Author

@rkangast I don't think it's fixed still get latest as 5.13.0?

@rkangast
Copy link
Contributor

@abbjetmus Latest is 5.14.0 and should be found with CocoaPods, see https://github.com/CocoaPods/Specs/tree/master/Specs/1/d/4/PolarBleSdk/5.14.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants