# Miscellaneous
*.class
*.log
*.pyc
*.swp
.DS_Store
.atom/
.build/
.buildlog/
.history
.svn/
.swiftpm/
migrate_working_dir/

# IntelliJ related
*.iml
*.ipr
*.iws
.idea/

# The .vscode folder contains launch configuration and tasks you configure in
# VS Code which you may wish to be included in version control, so this line
# is commented out by default.
#.vscode/

# Flutter/Dart/Pub related
**/doc/api/
**/ios/Flutter/.last_build_id
.dart_tool/
.flutter-plugins-dependencies
.pub-cache/
.pub/
/build/
/coverage/

# Symbolication related
app.*.symbols

# Obfuscation related
app.*.map.json

# Android Studio will place build artifacts here
/android/app/debug
/android/app/profile
/android/app/release

# Golden-comparison debris. `flutter test` writes four PNGs per failing shot
# (isolatedDiff / maskedDiff / masterImage / testImage) and regenerates them on
# every failing run — 128 of them were sitting untracked. The references
# themselves live in test/shots and ARE committed; these are the diff output.
test/failures/

# ── Signing material never goes in the repo ──
#
# `android/key.properties` holds the keystore passwords in plain text and the
# `.jks` files are the signing keys themselves. Anyone with both can publish an
# update to the app under its own identity, so a copy in git is a copy in every
# clone, every fork and every CI cache, for as long as the history exists.
#
# The keys that were already committed (nearlerider-keystore.jks,
# release-key.jks) are unused — the app signs with a key generated outside the
# repo — but they are still in the history and should be treated as public.
# They are left tracked deliberately: removing them from the working tree does
# not remove them from history, and rewriting history is the repo owner's call.
#
# Keep the keystore and its passwords in a password manager or a CI secret
# store. Losing them means never being able to update the app on Play again.
android/key.properties
*.jks
*.keystore