-
Updated
Feb 1, 2021
trackers
Here are 71 public repositories matching this topic...
-
Updated
Feb 2, 2021
-
Updated
Jan 18, 2021 - Shell
Currently there is a bug with application which versions / version codes have more than 50 characters.
This is not handled properly so the analysis hangs forever with the message "Tracker analysis: success"
Example: https://play.google.com/store/apps/details?id=ch.sbb.mobile.android.preview and its version flavorpreviewRelease-10.0.0.191210.1822.126-RELEASE
Couple of possible solutions:
-
Updated
Jan 8, 2021 - Jupyter Notebook
-
Updated
May 25, 2020 - Shell
-
Updated
Dec 11, 2020 - Python
-
Updated
Oct 8, 2018 - Shell
-
Updated
Feb 2, 2021
-
Updated
Jan 27, 2021
-
Updated
Jan 11, 2019 - Python
We have a function which purpose is to validate signatures (code & network) before they are saved in order to make sure they are valid regular expressions.
I think there is no case where we should have a space in our regexp and we could use this function to prevent this (already happened ;))
-
Updated
Jan 30, 2021 - M4
-
Updated
Jun 12, 2020 - Python
-
Updated
Jan 30, 2019 - Python
Improve this page
Add a description, image, and links to the trackers topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the trackers topic, visit your repo's landing page and select "manage topics."


The problem
Some embed scripts use data- attributes which clash with those used by klaro! - for example, one embed script I have come across has a data-type='inline' attribute, which breaks the script when it is changed to type='inline'.
Proposed solution