Quick tip on how to remove Git submodule.
git rm --cached path_to_submodule |
(without trailing slash)
As Android developer I have various mobile devices (phones, tablets, watches) with all Android version starting 4.0 (Ice Cream Sandwich, API 14) up to Android 12 (L, API 31). Those devices accompanied by very detailed test scenarios help me ensure best possible user experience 🙂
As Android developer I have various mobile devices (phones, tablets, watches) with all Android version starting 4.0 (Ice Cream Sandwich, API 14) up to Android 12 (L, API 31).
When prepping release for an app, all test cases for that particular app are performed on each device. For each Android version I keep track of active installs and user rating. Applying that data in the test scenario. This helps me focus more on particular set of for ex. unhappy users running specific OS version.
Below is a screenshot of a test scenario for one of my apps: GSM Signal Monitor & SIM Card Info.
GSM Signal Monitor & SIM Card Info test scenario
Each Android version has number of active installs and rating. Going to Google Play Store dev console and collecting this information by hand is somehow tedious job, so I decided to automate it using ‘Google Cloud Storage Util‘ and a bit of Windows PowerShell scripting.
Our task is to fetch Google Play store monthly reports for app installs and ratings by OS version, filter them and get data that can easily be copy pasted in the ‘Active Installs‘ tab of the test scenario.
Google Play reports, beside dev console can also be accessed via Google Cloud Storage bucket associated with your developer account. You can go to “Download reports”, pick the report type you want and select “Copy Cloud Storage URI” next to it.
Google Play Cloud Storage URI
The url will look like this
gs://< bucket_id >/stats/installs/ |
where < bucket_id > will be your actual developer account cloud storage bucket. Remember this bucket id. We will be using it later.
Google provides GSUtil for using cloud storage from the command line. Head over to https://cloud.google.com/storage/docs/gsutil_install#expandable-1 and follow the installation instructions.
We will be utilizing the gsutil.cmd assuming that the script is available in system PATH.
Next we need to authorize gsutil to access our cloud storage data. Follow the instructions on how to Authenticate stand-alone gsutil. For ‘project-id’ use the project ID of the app you want to get reports for. I’m interested in retrieving reports for GSM Signal Monitor & SIM Card Info app so I will be using it’s Cloud Storage project id.
Cloud Storage Project ID
If everything is setup correctly, opening command prompt and typing “gsutil help” should produce result similar to the screenshot below:
gsutil help command output
Script below will fetch installs and ratings reports from Google Play for specific app for the current month. Will get the last date available in the install report, filter both install and rating reports by ‘last available date’ and strip the reports from rows / columns we are not interested in. It will iterate over the active installs and will try to match installs with the ratings.
Replace $bucketId and $appPackageName with your cloud storage bucket id and your app package name.
Reports fetched from Google Play and the final output will be saved in the current working directory.
Upon execution you will get a report for your app active users/ratings by Android version, based on the data for the last date available in the install report nicely opened in your default text editor.
Script output: Active users and ratings.
P.S: Enable column selection mode in Notepad++ to get only the numbers. Use the arrow keys or your mouse while holding Shift + Alt.
P.S1: More info on how to retrieve various reports with gsutil here.
Feel free to modify the script to suit your reporting needs 🙂
If you liked this article and think it is useful use the buttons below.
Once upon a time all my Android apps and VMSoft related stuff were part of one big BitBucket git repository along with an issue tracker. This was a good idea when being an Android dev was just a hobby for the weekends and not my primary job.
Enough rambling 🙂 , this blog post is about moving files from one git repository to another and preserving your history.
Our goal is to move a single directory from one big Git repository to it’s own repository, we would like to preserve the commits history for that specific directory also.
In this example our big repo will be called A and our new repo that will host it’s own subset of files will be called B
First filter the files from the big repo (A) by leaving only the ones you need:
git clone < repo A url > cd < repo A directory > |
Remove the “origin”
git remote rm origin |
and filter A by < directory_to_move >. This action will go trough all the history and files and remove anything that’s not in < directory_to_move >.
More info on the inner workings of git filter-branch here.
git filter-branch --subdirectory-filter <directory_to_move> -- --all |
filter-branch will leave you with the contents of < directory_to_move > in the root of repository A. Commit the changes and we can continue with the next step.
git add . git commit |
Moving to the new repository
Link repo A with repo B. The command below will make repository A branch of repository B.
git remote add repo-A-branch <git repository A directory> |
Pull from the branch allowing unrelated histories
git pull repo-A-branch master --allow-unrelated-histories |
and finally remove repo-A-branch
git remote rm repo-A-branch |
That’s it, you now have your files in a new repository while preserving commits history.
If you liked this article and think it is useful use the buttons below.According to the msysgit wiki on GitHub and the related fix this error, Filename too long, comes from a Windows API limitation of file paths having 260 characters or fewer.
To resolve this issue, run the following command from GitBash or the Git CMD prompt (as administrator):
git config --system core.longpaths true |
This will allow file paths of 4096 characters.
If you liked this article and think it is useful use the buttons below.
I often work with HEX colors and want to apply some alpha to them.
Calculating the exact alpha HEX value is tedious job so here it is: the complete list of every possible opacity value in HEX
100% — FF 99% — FC 98% — FA 97% — F7 96% — F5 95% — F2 94% — F0 93% — ED 92% — EB 91% — E8 90% — E6 89% — E3 88% — E0 87% — DE 86% — DB 85% — D9 84% — D6 83% — D4 82% — D1 81% — CF 80% — CC 79% — C9 78% — C7 77% — C4 76% — C2 75% — BF 74% — BD 73% — BA 72% — B8 71% — B5 70% — B3 69% — B0 68% — AD 67% — AB 66% — A8 65% — A6 64% — A3 63% — A1 62% — 9E 61% — 9C 60% — 99 59% — 96 58% — 94 57% — 91 56% — 8F 55% — 8C 54% — 8A 53% — 87 52% — 85 51% — 82 50% — 80 49% — 7D 48% — 7A 47% — 78 46% — 75 45% — 73 44% — 70 43% — 6E 42% — 6B 41% — 69 40% — 66 39% — 63 38% — 61 37% — 5E 36% — 5C 35% — 59 34% — 57 33% — 54 32% — 52 31% — 4F 30% — 4D 29% — 4A 28% — 47 27% — 45 26% — 42 25% — 40 24% — 3D 23% — 3B 22% — 38 21% — 36 20% — 33 19% — 30 18% — 2E 17% — 2B 16% — 29 15% — 26 14% — 24 13% — 21 12% — 1F 11% — 1C 10% — 1A 9% — 17 8% — 14 7% — 12 6% — 0F 5% — 0D 4% — 0A 3% — 08 2% — 05 1% — 03 0% — 00 |
How to use it:
#000000 – Black with ought opacity
#17000000 – Black with 9% opacity