Conversation
|
Awesome, thanks for the cleanup! A couple of questions:
|
I saw this exception on https://github.com/KarimAbdo/FlutterGeofencing: I can see that this is not an issue on your project. So I removed that change again.
I am not the one who published it. From what I can see this: https://pub.dev/packages/geofencing was published by axella.gerald@gmail.com. Furthermore the fork from https://github.com/KarimAbdo/FlutterGeofencing seems to be published as well: https://pub.dev/packages/flutter_geofencing I have reverted a few extra minor things to minimize the diff. |
|
I tried registering a geofence again. After a little time I got the exception below. I will add the change that executes on the main thread again: |
This reverts commit b2a2f73.
LICENSE
Outdated
| @@ -1 +1,5 @@ | |||
| TODO: Add your license here. | |||
| Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: | |||
There was a problem hiding this comment.
Can you remove this license? I'll need to update this to match the licenses in the actual source (whatever the Flutter project uses).
android/gradle.properties
Outdated
| @@ -1 +1,3 @@ | |||
| org.gradle.jvmargs=-Xmx1536M | |||
| android.useAndroidX=true | |||
There was a problem hiding this comment.
Really nitpicky request, but can you ensure this file is sorted alphabetically?
That's interesting, I'm surprised I've never run into that myself (unless it's happening and it's only being logged without bringing up a crash dialog). It looks like you're right though as my colleague made a similar change to the
Ah, sorry about the confusion. GitHub names don't always match to Pub developer emails so I just made a bad assumption :-). |
There are a few fixes here: