Full circle with a gap at 11 o'clock

Some time ago I've claimed that I've run a full circle on a TLS certificate lifecycle. Well, there was one more kink in that circle that I've failed to acknowledge at the time.

No version is technically a version

 Amazing discovery of the day: if your Android application doesn't link against the Google Play billing library, but claims to use the com.android.vending.BILLING permission in the manifest, the Google Play developer console will turn your APK down, saying that it uses an unsupported version of the billing library, and why won't you upgrade to v4.

If your app links against billing v5 (the latest as of the time of this writing) but lists said permission in the manifest, you will receive the same error message.

The problem of repeated crashes

Postmortem app crash reporting and analysis is a bit of a hobbyhorse for me. I see it as an extension of the bug reporting facility - a crash in production (typically, but not always) indicates a bug. But does every crash indicate a separate, distinct bug?

Project vs. collection

Some time ago, I've discussed the identity of the account that TFS agent jobs are using to connect back to TFS via the distributedTask PowerShell context variable, or the equivalent System.AccessToken release variable. Back at the time, I've concluded that the identity behind that token was "Build Service (CollectionName)". Well, just today I've encountered a case where a release was running under a different identity - "ProjectName Build Service (CollectionName)". Both coexist.