transistorsoft / background-geolocation-firebase Goto Github PK

I have followed the steps for the Android implementation, but on building, I get:

Running Gradle task 'assembleDebug'...
/Users/tim/dir/work/src/iDriver/android/app/src/main/java/au/net/ideliver/idriver/MainActivity.java:17: error: cannot find symbol
TSFirebaseProxy firebaseProxy = TSFirebaseProxy.getInstance(getApplicationContext());
^
symbol: class TSFirebaseProxy
location: class MainActivity

It feels like I am missing an import statement for the MainActivity class.

Would you have any clues as to why it doesn't recognise TSFirebaseProxy?

The plugin `background_geolocation_firebase` uses a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to see if this plugin supports the Android V2 embedding. Otherwise, consider removing it since a future release of Flutter will remove these deprecated APIs.
If you are plugin author, take a look at the docs for migrating the plugin to the V2 embedding: https://flutter.dev/go/android-plugin-migration.

Here's my flutter doctor:

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.5.0, on macOS 11.2.1 20D74 darwin-x64, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.1)
[✓] VS Code (version 1.60.1)
[✓] Connected device (2 available)

• No issues found!

I'm still at the R&D stage and have a prototype app which uses the background-geolocation plugin with the additional background-geolocation-firebase plugin. GeoLocations are feeding into my Firestore database as expected.

The default Firestore security rules allow read/write to any user, which I will need to resolve before I can complete the R&D project. If I change the security rules to restrict access to authenticated users, the Firestore plugin can no longer write to the database.

I cannot see any provision for user authentication in the plugin documentation. Have I missed it or do you have any plans to implement in the future?