Did you check how many devices your app is compatible with in the Play 
console? Especially if you're using the new UI -- which seems to 1) be more 
strict with its manifest parsing and 2) has poor error reporting.

I once got burned by this, where a small omission in the manifest (IIRC, I 
forgot the "android:" part on some attribute) was causing the app to be 
compatible with "zero" devices in the new console, and yet has been working 
fine before I switched (to the new Play console UI).

-- K

On Wednesday, February 6, 2013 10:11:37 PM UTC+4, Greg Donald wrote:
>
> Yesterday I shipped a bug fix update.  The update is a workaround for 
>
> http://code.google.com/p/android/issues/detail?id=7189 
>
>
> +import android.view.MotionEvent; 
>
> [...] 
>
> +    add_phone.requestFocus( View.FOCUS_DOWN ); 
> +    add_phone.setOnTouchListener( new View.OnTouchListener() 
> +    { 
> +      @Override 
> +      public boolean onTouch( final View v, final MotionEvent event ) 
> +      { 
> +        switch( event.getAction() ) 
> +        { 
> +          case MotionEvent.ACTION_DOWN: 
> +          case MotionEvent.ACTION_UP: 
> +            if( !v.hasFocus() ) 
> +            { 
> +              v.requestFocus(); 
> +            } 
> +            break; 
> +        } 
> +        return false; 
> +      } 
> +    } ); 
> + 
>
> With that change users running Android 2.3.x can now get a keyboard 
> when they click into my WebView form fields, yay! 
>
> But then this morning a long time user sent me a screen shot of Google 
> Play telling him his device is not compatible with my app! 
>
> I have reviewed my git commit and nothing changed except a few lines 
> of Java you can see above, and the version numbers in my 
> AndroidManifest.xml: 
>
> -    android:versionCode="55" 
> -    android:versionName="1.1.2"> 
> +    android:versionCode="56" 
> +    android:versionName="1.1.3"> 
>
> No permissions changed, no SDK version changes, still at 2.2 just like 
> always. 
>
> Any idea how to fix this situation?  We're a SaaS company and via 
> Google Play I just killed his service because I simply shipped a 
> workaround for an Android keyboard bug. 
>
>
> -- 
> Greg Donald 
>

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to