It has been several months now and days and days of work that we have been trying to get Google to approve that our users can access their Google Drive again through iA Writer for Android. (They suddenly cut it off). Last week we supposedly passed the last test.

This week they come back and want us to downgrade the scope to read only. Read only? It's literally a writing app!

I think we're not dealing with humans but with an AI that just keeps wasting our time. I'm flipping-tables annoyed.

So we tell them that our users (not us) need read write access to Google Drive so they can write their texts, and they want us to go through a scanning process that takes at least 6 weeks. One of the suggested vendors for the CASA scan is KPMG.

It probably costs more than what we make with an app that has more pirate users than regular ones.

Guys, we want our users to be able to access their Google drive so they can write and stop 1-staring us for something we didn't do.

Close to giving up.

They want us to do this CASA certification with KPMG or similar every year. In the mean time we're getting hammered with bad reviews as users think it's our fault.

Instead of fixing their crappy core frameworks (often people can't pay for apps they want, or they pay and Play Store forgets) Google keeps us busy updating this, complying that. I just sent them a stack of paper last week.

Both Apple and Google are squeezing devs with the same percentages. But at least Apple's stuff works.

@reichenstein it honestly is such a waste of time… for our open source app that also runs on the users machine, I went through the self scanning process and submitted the results. It was so hard to figure out that we could just do it ourselves than to pay some firm that looks at our scan results, that we needed to prepare anyway.
At multiple places theres just no option that suits „local app on the users machine“, to the point I was tired typing that into the „N/A“ comment field.
@reichenstein It did not even import the export of one of their recommended open source scanning tools. I had to go back and forth with pwc support (the company is running the submission portal) to sort it out. Unsurprisingly and fitting for the absurd process, what I submitted was an empty file, because there were no vulnerabilities according to their configuration.
@reichenstein We did not need to pay an external vendor, but it took a significant amount of time that I am really not looking forward repeating next year…
I hope they forget or cancel/rethink this program.
@_pillepalle_ From what we learned, it seems that in the mean time they changed it again. There's no V2 anymore, so next year you can't do it yourself.
@reichenstein Oh, well, that‘s a bummer. But thanks for the heads-up! It still boggles my mind how they could greenlight this security theatre that we have to pay for now. But I’m not surprised they „forgot“ native apps that use Drive as, well, just a drive.