I wrote back to explain that yes – my app is using https. They respond to say that ‘If, after making changes, you think your app is in compliance, please submit your app for another review.’

I clarify that I’m not making any changes – because none are required and resubmit.

25th May: They respond to say

Good news – I see your app, VLC Remote (com.hobbyistsoftware.android.vlcremote_us), was resubmitted earlier and has been approved.

Second Removal

29th May: A Very Similar Message

After review, VLC Remote, … has been removed from Google Play because it violates our personal and sensitive information policy … This app won’t be available to users until you submit a compliant update.

We go through the same dance. I explain that it isn’t violating their policy. It does send the user’s email to my server, but only when explicitly asked to – and over https.

They approve the resubmission.

Seriously – Again???

6th June:

After review, VLC Remote, com.hobbyistsoftware.android.vlcremote_us (Version Code: 47963), has been removed from Google Play because it violates our personal and sensitive information policy

The focus now is on ‘Prior to the collection and transmission, it must prominently highlight how the user data will be used, describe the type of data being collected and have the user provide affirmative consent for such use.’

I’m lost for words here. Supposedly, someone has reviewed the app. And they have looked setup help process. They clicked on ‘yes send me details’ then entered their email address, clicked ‘Send’ and they consider that I haven’t been clear about what is going on.

Incidentally – I had the exact same process with VLC Streamer on 20th March.

And of course my app is off the store – and not making any sales

I’ll build again, submit again and see what happens. This is getting very boring though…

Removed again – despite already being removed, and not having resubmitted yet!

13th June:

After review, VLC Remote, … has been removed from Google Play because it violates our personal and sensitive information policy

Your app is uploading users’ email information to … without posting a privacy policy in both the designated field in the Play Developer Console and from within the Play distributed app itself. Your app must also handle user data securely, … (for example, over HTTPS).

I’m guessing that my ‘this is ridiculous’ email triggered a review.

This time, the primary objection is that the app must have ‘a privacy policy in both the designated field in the Play Developer Console and from within the Play distributed app itself’

Of course – I do.

I know this because on the 29th May, VLC Remote was removed for exactly that reason.
On the 29th of May – it was correct. I did have a privacy policy linked in the store – but it wasn’t within the app itself. This app has been up for years, and I don’t know when the requirement came in to have the privacy policy within the app.

Anyway – after the email of the 29th of May, I sent in an update which added the privacy policy into the app within the settings page. I resubmitted and was approved.

At the time, I thought it was ridiculous that Google would remove the app from the store immediately over a violation like this. They could easily have sent me an email and given me (say) 7 days to put things right.

It was more ridiculous than removing me for the same reason _after_ I have fixed the problem.

btw; In the Apple store, when you submit an app for review, there is a ‘reviewer notes’ field. You can use this to let the reviewer know anything you think is important.

For example you might let them know where the privacy policy was shown (in the settings) – or that you always upload sensitive data over https. Google has nothing like this, and clearly doesn’t keep notes on review decisions / appeals.

I’m going to respond to the latest email with a link to this blog post. We’ll see what happens.

Update 18th June

I submitted yet another appeal. This time with a google doc to explain what was going on.

The response looked like the old rejections – but in the reviewer did helpfully highlight the version number.

It turns out this is an old build uploaded in 2016 which targets users on API level 14. There are 20 active installs.

I disabled all the old versions of the app, resubmitted, and (so far) everything is live.

(Hopefully) Final Thoughts

The Apple review process can be infuriating. Apple have some rules that seem ridiculous to me, and they’re seldom flexible about applying them. However, they communicate clearly – as real people. When there is a minor issue, they’ll ask you to fix it rather than just booting you out of the store. They also seem able to keep notes about previous discussions and if they have resolved one issue – they won’t come back to it again.

By contrast – Google make it seem like you’re dealing with a badly programmed Eliza-Bot.

There is no context in their replies – they just bang out the same template letters with no acknowledgement of any points, requests or comments you have made.

I’m wondering if they are forbidden from sending out personalised emails – and have to resort to highlighting as the only marginally personal communication method available to them.

I never got any acknowledgement that the first four removal reasons were completely without merit. But my app spent weeks out of the store because of them.

The final rejection felt like they were scraping the barrel to justify the removal – and although it was probably true (I haven’t checked) – the particular version was only used by 20 devices, and had been in place since 2016, so they could have either disabled that one version, or approved the app and asked me to do that within (say) 7 days.

This whole process was deeply frustrating – and in the end, no changes have been made to the builds which triggered the first bunch of rejections.

We have a handful of updates to address some minor problems with Windows 10.

VLC Streamer is now updated to 5.07, and Watchover is now at 1.20.

Windows 10 is now available for public beta – so if you’re using it, do let us know of any other issues or problems you come across. We’d love to have the kinks worked out before the official Windows 10 release.

Like many of my favourite apps – this one springs out of an annoyance that I wanted to fix.

If you have used windows, then you may well have used one of the many right click commands in the finder. Some of these are built in, and some are added by third party apps.

Two that I particularly miss are

‘Make untitled.txt here’

and ‘Open this directory in the terminal’

Mac OS has had the ability to use custom scripts as services – but they’re too far from the right click to be useful (right click, scroll down hover over services, skip right, find the command you need).

Finally – with the advent of Yosemite and finder extensions, Mac OS has an approved way for me to fix this.

Enter the Sandbox…

The app sandbox is designed to make sure that apps you download from the App Store can only interact with a limited selection of files (mostly within your own app sandbox).

The app I wanted to build lets you add, open or update files anywhere in the system.

If you want your app to be in the App Store – then it has to use the sandbox!

There is a (clunky) solution

Right click booster is a developer tool, and I wanted developers to be able to integrate their own scripts.

There is actually a way that Apple lets you do this.

Scripts can be run from the User Script Directory (every app has it’s own user script directory).

This seems like a great solution, but the app isn’t allowed to put scripts in that directory.

In my first submission, the app asks the user to open the directory – thus giving permission to the app to read and write files there. Apple didn’t like that.

In my next submission, I included the scripts in a .dmg file. My app can include the .dmg, open it and let the user drag scripts to the symbolic link to the user scripts file. Apple didn’t like that either.

In my final submission – the app takes you to my website where you can download the default scripts (as a dmg). Open that dmg, and install the scripts yourself.

There were many other issues along the way – but finally, Apple have allowed this solution.

Now you can run scripts with a right click

I use my app all the time!

The ones I use the most are Pod Update, and Update version (this runs ‘avgtool next-version -all’ which bumps the version number for all my targets in an xcode project)

My other favourites are the two I built the app for. ‘Open this directory in the terminal’ and ‘Create untitled.txt’ here.

Of course, other users will have other scripts and other ideas.

If they’re generally applicable, then I’ll add them to the default script list – so please do share them at the forum!

I assume that Chromecast will get better over time, and I’ll give it a try again in a few months.

Unfortunately, my expectation of Chromecast is not necessarily one that the Chromecast team share. I expect Chromecast to ‘just work’.

If streams play on iOS and Android, then I don’t expect to have to battle to format them specially for Chromecast. Equally, I expect integration to be simple rather – whereas the Chromecast team expect me to implement a whole complex system of searching and communication.

For the most part – the Chromecast team response has been to refer to state that vlc streamer steams don’t meet the required specification and that any crashes are therefore not Chromecast’s problem.

You can see the lively discussion here. It’s one of the most +1’d posts on the ChromeCasst developer forum. I think that means I’m not the only frustrated developer.

As a Chromecast owner, I’m not sure what you can do. The fact is that Chromecast is hard to integrate – and doesn’t do a good job with HLS streams. Until the Chromecast developers fix that – VLC Streamer won’t be supporting Chromecast.