reset market license

by ruspa » Fri, 28 Jan 2011 18:51:18 GMT

Sponsored Links
 I got some issues with my market license key.. I've read about how LVL
check fails with ApiException 503 error for preventing dos
attacks..etc.. but now I'm getting this error on my own phone and
can't run or debug in no way the app.
How can I reset the market LVL timer or change my keys? I've been
waiting for a couple of minutes without requesting LVL validation but
keeps on going 503 error....


Re: reset market license

by ruspa » Fri, 28 Jan 2011 19:02:08 GMT

 there should be a way to kill the feature that detects this "dos
attack", it's impossible to test effectively something without running
the piece of code dozens and dozens of times. If the market
verification fails after a couple of trials it's quite disappointing.
Plus, this 503 issue (ops should have I said "feature") is poorly
documented, I found only instructions saying
"try not to hit the market too often or you will start getting 503
errors, and it will take a while to reset"
Wth it means? How much is exactly "a while"? I'm sick of waiting :(


Sponsored Links

Other Threads

1. How to use android:required


In my manifest file, I have the following:

    <uses-permission android:name="android.permission.CAMERA" />
    <uses-feature android:name=""/>

my app can use the camera if one exists, but is not necessary for the
app to function. My app also uses the auto-focus callback when taking
a picture, but is not required, thus it is not listed as another
hardware listing above.

If I read the docs correctly, after 1.6, we need to specify which
hardware features are necessary for our app to run, otherwise if we
leave that section blank, it's assumed that all features are required.
So I thought to only add the most basic on,

Does this mean that when placed on the market, my app will not show up
for devices without a camera, as my manifest stands now?

In this post:


2. The meaning of open

The Google blog just had an interesting post on the idea of "openness"

I wonder if this will have any impact at all on developing Android in
the open or increased acceptance of community participation.

I particularly found these two quotes interesting and relevant:
"And when you do, do it right; don't just push it over the wall into
the public realm and forget about it."
"There are risks to this approach, however, as the software can
fragment into different branches which don't work well together."

I don't necessarily know that Google could be handling things better.
Working with all the OEMs and partner companies that don't operate on
the same principles of openness certainly must be a challenge, and one
that most of us can only hypothesize about. But it would be
interesting if there was a blog post about what advantages to the
consumer stem from Android's non-adoption of transparency and openness.


3. Using new sdk methods on devices running older sdks?

4. The GPS Shutdown Thing

5. How to implement the concept of purchasing credit?

6. Will the droid with andoid 2.0 get updates that give us more home screens>?

7. Define what activity will start the task on Recent Apps menu