# WBA Bearing Authenticator 2.0 — user reviews

> 3 indexed App Store user reviews of WBA Bearing Authenticator 2.0 by oneIDentity plus GmbH, rated 2.00/5 from 7 ratings.

- Source: https://appshunter.io/ios/app/wba-bearing-authenticator-20/id1672612450/reviews
- App overview in markdown: https://appshunter.io/ios/app/wba-bearing-authenticator-20/id1672612450.md
- Rating breakdown: 5★ 1 · 4★ 0 · 3★ 1 · 2★ 1 · 1★ 4

## Most critical reviews (3 lowest-rated)

### 1/5 — Doesn’t work

*2025-04-30*

Attempted use with SKF bearings. “Unknown string response” was what it responded at every attempt.

### 1/5 — Doesn’t work

*2024-11-23*

Every time I’ve used it I get the message to try again in a few minutes.

### 3/5 — It’s got a good foundation but NEEDS more testing before release

*2025-01-10*

First of all the scan option for the camera isn’t capable of switching between a phones normal and macro cameras as a result you can’t capture small product ID images. I was able to create a work around by using a magnifying lens so that the camera could focus on it for the auto capture to work. 

Second the scan code option that allows you to scan codes while offline then validate later only returns the same response “OK” despite the exact same code earlier through the check now feature returning an unknown or invalid message. So unless somebody happened to authenticate my product’s code between checks that response might be the default or it might only be referring to the very first code i scanned in the list for checking later and not the later ones. 

Third while syncing the app it crashed upon completion but proceeded like normal continuing from where it left off after start up again. The app also crashed while submitting a fake bearing report. Spent 20min documenting the packaging and product from multiple angles and close ups along with cropping pictures so whatever they receive they have the best chance at determining if it’s real or not. I have no idea if the report ever finished being submitted successfully, as the progress bar appeared to stall out at 70% for awhile before the app crashed on me… if it hadn’t been for the initial syncing doing something similar I would be a little more dismayed thinking I wasted a bunch of time for nothing but I at least have marginal confidence it could have gone through.

Either way all of these issues are a problem for reliability and not acceptable for a professional app. I would say it’s at a BETA level but needs thorough testing in many different devices so these issues don’t discourage users from the goal of actually checking authenticity and helping report the spread of counterfeiting.

---

*Data collected daily from the US App Store and indexed by [AppsHunter](https://appshunter.io/). User reviews are verbatim App Store reviews. Ratings, prices and chart positions refresh continuously; this snapshot is from 2026-08-11.*