Versioning
Fidbek SDKs follow semantic versioning:
MAJOR: backward-incompatible changeMINOR: backward-compatible feature additionPATCH: backward-compatible fixes
Current documented release line
The current docs target the 0.3.0 SDK line.
0.3.0 cross-SDK highlights
- Added issue frequency selector in bug flow (
occurrence_frequencyin payload). - Added built-in localization for
en,tr,es,fr,de,pt,ar,hi,ja, andzh-Hans/zh-CN. - Added automatic fallback to English for unsupported device locales.
- Added optional persisted SDK identity with
userId,name, andemail. - Added contact email prefill from identified user email.
- Added SDK version text in category dialog (
Fidbek vX.Y.Z). - Improved reliability:
- token validation now runs at report submit/send time.
- device heartbeat ping + queue behavior added for resilient delivery.
Trigger behavior updates
- iOS uses native motion shake handling.
- Android shake detection is tuned to reduce accidental opens.
- Manual trigger remains recommended in Settings/Help for production UX.
Wrapper package notes (0.3.0)
- React Native (
@saltware/fidbek-react-native) and Flutter (fidbek_flutter) intentionally expose the same 5-method surface:configureopenidentifyclearIdentityshutdown
- Both wrappers bundle refreshed native artifacts:
- Android:
fidbek-android.aar - iOS:
FidbekSDK.xcframework - iOS resources:
FidbekSDKResources.bundle(en,tr,es,fr,de,pt,ar,hi,ja,zh-Hans)
- Android:
- Deprecated native attachment staging helpers are not part of wrapper APIs.
Upgrade strategy
- Pin versions in production apps
- Run iOS + Android smoke tests before rollout
- Keep docs and release notes aligned with published artifacts
- Prefer minimal integration:
- configure once
- identify when the app knows the user
- clear identity on logout