'Allow analytics' always re-enables itself
See original GitHub issuemacOS Version: ProductName: Mac OS X ProductVersion: 10.13.6 BuildVersion: 17G65 Kap Version: Version 2.2.0 (2.2.0.880)
Steps to reproduce
- Open Kap
- Open Preferences
- Disable ‘Allow analytics’
- Close Preferences
- Open Preference
- Note that ‘Allow analytics’ is now re-enabled
Current behaviour
‘Allow analytics’ preference either never saves or re-enables itself without warning.
Expected behaviour
‘Allow analytics’ preference should respect my choices.
Workaround
Firewall Kap off from hitting Google Analytics.
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
29 Common Google Analytics Data Errors And How To Fix Them
Google Analytics data not showing all traffic or no view data? Here's why your data is wrong and how to fix the most...
Read more >Consent Settings In Google Tag Manager | Simo Ahava's blog
The Consent Mode initial config sets the default state of ad storage as denied and analytics storage as denied. That's all it does....
Read more >What's new - Analytics Help - Google Support
As of October 14, 2020, a Google Analytics 4 property (formerly known as an "App + Web" property) is now the default when...
Read more >7 Steps to Ensure and Sustain Data Quality | by Stephanie Shen
Consistency:the data should have the data format as expected and can be cross reference-able with the same results. The standard for good data ......
Read more >Azure Storage Analytics logging | Microsoft Learn
Use Storage Analytics to log details about Azure Storage requests. See what requests are logged, how logs are stored, how to enable Storage ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Bummer. Since we haven’t heard about this issue in the past and things seem to work with 3.0 (which should be stable enough, just keep an eye out for the beta so you remember to update), I’m going to close this issue for now. Again, thank you for the issue and quick replies, glad we could find a workaround.
Doesn’t work unfortunately; running 2.2.0 leads to
Settings
being recreated, with its original settings. In that file is a bundle of JSON with the same object as what’s inconfig.json
. So the two versions seem to use different config filenames.Anyway, I’m fine with using v3 if it’s stable enough. Otherwise, modifying the
Settings
file seemed to workaround the problem for now…