Disabled app but still getting billed for it.

[David Hardwick]

Hello,

I've notice that I have apps that have been disabled for a while but I'm still getting the $2.10/week minimum charge.  I then went and disabled billing as well for the app.  

Do you always have to both disable the app and the billing?

Regards,

  - Hardwick

[Gwyn Howell]

Same thing happened to us. It seems you have to disable billing before disabling the app or they'll continue to charge you.

[Jeff Schnitzer]

Sounds like a bug - have you logged an issue here?

http://code.google.com/p/googleappengine/issues/list

Jeff

> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/zJy1lu3kq-AJ.
>
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengi...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.

[Barry Hunter]

Yes. Google have said this is intentional.

An app - even disabled, could be using chargable services. Most
noteably storage.

So to stop being changed for an app - you need to explicitly disable
billing. A prerequisite of such, is that your app doesn't need more
than the free quota.

[Jeff Schnitzer]

Hah! So that's how they're trying to get around "just abandon the app
instead of deleting all your data".

I'm curious to know what happens when people simply change their CC#.

Jeff

[David Hardwick]

Okay, that makes sense that you could be using other services even
though the app is disabled. However, it would be nice to get a warning
when you disable your app to let you know you need to disable billing
too if you are not using other services.

The whole "don't be evil" principle applied here would at least garner
a modal window to let you know to disable billing if you are not using
any other services and are willing to nix your data, etc.

On Apr 3, 7:27 pm, Jeff Schnitzer <j...@infohazard.org> wrote:
> Hah!  So that's how they're trying to get around "just abandon the app
> instead of deleting all your data".
>
> I'm curious to know what happens when people simply change their CC#.
>
> Jeff
>
>
>
>
>
>
>
> On Tue, Apr 3, 2012 at 6:43 PM, Barry Hunter <barrybhun...@gmail.com> wrote:
> > Yes. Google have said this is intentional.
>
> > An app - even disabled, could be using chargable services. Most
> > noteably storage.
>
> > So to stop being changed for an app - you need to explicitly disable
> > billing. A prerequisite of such, is that your app doesn't need more
> > than the free quota.
>

[Jeff Schnitzer]

My guess is that this really hasn't been thought out very well and is
just getting worked out now.

Deleting data is way more complicated than creating it, and overall it
seems less important - it's for customers who are leaving. Seems like
all startups are this way; ours is no exception. When you delete an
athletic event in Voost, there are all kinds of potential messes - has
anyone registered for the event? are there foreign key references to
it?

From GAE's perspective, the smart thing to do is charge double for
writing the data and make deleting it free. It's like including the
recycling fee with the soda can purchase. Not sure why they didn't do
that.

Jeff

[Stefano Ciccarelli]

I have an app with billing disabled and storage over quota. 

The main point is that disabling an app is not like disabling billing, they are two different operations. 

-- 
Stefano Ciccarelli

Sent with Sparrow