Closed virtualmarc closed 11 months ago
Thanks for reporting, I could reproduce! This will be fixed with the next update.
Also based on our understanding the event contains no personally identifiable information so the GDPR does not apply here.
The event contains the full pubspec.yaml file which is personally identifiable.
Theres also a unique user id generated on the first build to track user's across multiple projects. This is a direct identification of a single user.
Here is an example from my machine:
[{"event":"Build","properties":{"distinct_id":"uhSFb+jsjGA","Tool":"Dart Generator","Version":"2.0.0","Dart":"3.0.0","Flutter":"false","BuildOS":"windows","BuildOSVersion":"\"Windows 10 Pro\" 10.0 (Build 22621)","lang":"de","c":"DE"}}]
The distinct ID allows to de-duplicate events, yes. However, it does not allow us (and we also do not intend to) in any way to find out who you are (e.g. your name, address, email address, etc.)
Fix available with release 2.1.0
! Get it with flutter pub upgrade
(or dart pub upgrade
for Dart Native projects).
When I want to run the build runner and generate the sources, the object box generator fails with a HandshakeException and no sources are generated:
After some inspection of the generator code I could work around it by editing the analysis.dart and add a
return null;
at the beginning ofsendEvent
.The Build should not depend on external resources, especially tracking pages.
In many enterprise environments build and developer systems are limited and have no or restricted internet access. In my case the internet access is scanned by an interception proxy breaking the TLS traffic.
Basic info:
Steps to reproduce
Expected behavior
Access to unnecessary external resources should not fail the build process.
Tracking should be opt-in by GDPR (and the german DSGVO) Law and is not allowed to be always active without user input.