Works 15.2.1
Old app was left unsupported on Droid. Couldn't get the app to work with my S10 or S12. Switched to iPhone13 and pleasantly surprised the old app/device works! Nice!
Great data
App is up to date. Easy to install. Provides more data than anticipated. Well priced for its features
Works with iOS 14.2
I had the same problem as other reviewers. It would not work with iOS 11 to 13. I just upgraded to iOS 14.2 and it works now.
GSA putt device not compliant w latest iOS
This device is not compliant w iOS version 11 or higher...ridiculous. The company should either refund purchase price or fix compliance issues
GSA3Bays Putt
It does not make sense why this app has not been updated! Is there any timeline for update? Very disappointing.......
I just purchased a new device because my old one wouldn’t work on my newer iPad. I upgraded to iOS 11, and find out I can’t use the GSA putting device now. What the hell!
I just purchased a new device because my old one wouldn’t work on my newer iPad. I upgraded to iOS 11, and find out I can’t use the GSA putting device now. What the hell!
Not Updated in 4 Years
I purchased the put application when it first came out. I used it off and on and very much liked the information.
I bought a new iPhone and of course IOS has been updated. Support from the vendor says they’ve been unable to make the application under iOS 11.
Perhaps if they’d been updating it more often than 4 years ago it would still be working.
I bought a new iPhone and of course IOS has been updated. Support from the vendor says they’ve been unable to make the application under iOS 11.
Perhaps if they’d been updating it more often than 4 years ago it would still be working.
Show less
Need update for ios11
Won’t work unless they update.
Not working with newest 11 update.
Need to be updated guys.
Doesn’t work with iOS 11
...and now here I am with the worthless device I purchased!
Needs an Update
Will not connect with iOS 11 and I would really like to be able to use this device thru the winter for practice. Do you see an update to correct this in the near future?
