What the developer wrote
Authored by julian
fix: exception message
What changed, and why it matters
This commit simply corrects an error message text. When a part of the app called ShopInBitService is used before being set up, the thrown error now tells the user to call ensureInitialized() instead of the outdated init(). There is no security change.
No security action needed; treat as a routine string-correction commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff changes one Dart Exception string in lib/services/shopinbit/shopinbit_service.dart. The guard that throws when _secureStorageInterface is null now references the current initialization method name (ensureInitialized) rather than the old name (init). No logic, control flow, or security behavior is altered.
Changed components
lib/services/shopinbit/shopinbit_service.dartInspect captured patch +3 / −1
diff --git a/lib/services/shopinbit/shopinbit_service.dart b/lib/services/shopinbit/shopinbit_service.dart
index d8d2cee..b8b380a 100644
--- a/lib/services/shopinbit/shopinbit_service.dart
+++ b/lib/services/shopinbit/shopinbit_service.dart
@@ -10,7 +10,9 @@ class ShopInBitService {
SecureStorageInterface get _secure {
if (_secureStorageInterface == null) {
- throw Exception("Did you forget to call ShopInBitService.init()?");
+ throw Exception(
+ "Did you forget to call ShopInBitService.ensureInitialized()?",
+ );
}
return _secureStorageInterface!;
}
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.