Google Play seems to be set up under the assumption that the developer of
an app is also the publisher. This is not always the case and, as described
below, it causes us (and, I suspect, many others) a lot of time and
aggravation. I'm interested in feedback on whether others have encountered
I'm not sure I understand this suggestion. What state are you tracking? How
is it separate from what Google Play returns? As I described, we are
already separately maintaining the last definitive response received. Do
you do something beyond that?
More to the point: our app *seems* to be
We have an app that uses the following license policy:
- if a definitive response of LICENSED is stored in the app's
preferences and has not expired, allow access.
- if a definitive response is not stored in the app's preferences, or if
it has expired, or if the cached response is
Now that we have RTL text support in KitKat, I thought that a TextView that
displays a vertical scrollbar would by default display it on the trailing
side of the text. A simple experiment, though, shows that it always
positions the scrollbar on the right, even when the text is right-to-left.
for something that
needs to respond to events that aren't initiated by the user.
On Tuesday, September 24, 2013 7:35:26 PM UTC-7, Ted Hopp wrote:
In testing an app with in-app billing, we found a nasty problem that
occurs if there is a configuration change while a purchase flow is in
progress
In testing an app with in-app billing, we found a nasty problem that occurs
if there is a configuration change while a purchase flow is in progress.
The initiating activity is destroyed and restarted, breaking the link from
Google checkout process to the activity. To the user, it appears that
We have an app that was first submitted to Android Market several years
ago. We've published several updates and are preparing a new update. We
recently started receiving the following warning when exporting a signed
.apk file:
Certificate expires on Thu Sep 16 19:19:35 EDT 2038.
The
This is because of the activity
lifecyclehttp://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle.
When you call finish() from within onCreate(), none of the other activity
start-up events have occurred, so the corresponding shut-down events are
also skipped. This
On Thursday, June 14, 2012 12:43:51 PM UTC-4, Dianne Hackborn wrote:
The platform has an app signed with a cert. If you want to install an
update to that app under a different cert, how could the platform trust
that this is actually coming from the author who owns the original cert
Thanks for the lead, TreKing. It would be a big relief if Google disarmed
this time bomb. If you happen to run across the thread, I'd appreciate a
pointer to it; I definitely would like to follow any developments.
--
--
You received this message because you are subscribed to the Google
Groups
When an app crashes due to an uncaught exception, the user can submit a
crash report, that shows up in the developer console, showing a stack trace
and other useful information. But if the app catches the exception, it
doesn't crash and I don't know of a good way of receiving diagnostic
On Tuesday, June 25, 2013 5:02:43 PM UTC-4, a1 wrote:
You are attacking a strawman. I've commented on a very specific quote
from original post:
The alternative is to start removing catch clauses so that the app will,
in fact, crash and the developer can at least see something. This seems
I asked a version of the following on
StackOverflowhttp://stackoverflow.com/questions/11693100/would-this-google-play-licensing-policy-be-safe-to-useand
received only one response, which was off-point.
The default ServerManagedPolicy that Google provides in their License
Verification
The usual way to do this is to create a library project with the common
elements and then to create separate projects containing only those
elements of the app that are unique to each APK. See the docs on working
with library
You cannot control the values for VT, GT, GR and UT. The server sets these
values automatically (as described
herehttp://developer.android.com/guide/google/play/licensing/licensing-reference.html#extras
).
--
You received this message because you are subscribed to the Google
Groups Android
I'm not clear on what needs to be declared in the manifest file for a
library project. On the one hand, the documentation for setting up a
library project in
Eclipsehttp://developer.android.com/tools/projects/projects-eclipse.html#SettingUpLibraryProjectsays:
A library project's manifest file
Thanks, Adam. It seems that onSizeChanged is the way to go. I can cache the
last width passed in onSizeChanged and only trigger new work if the width
changes. I'm glad you pointed out that onSizeChanged can be called with 0
width; I wouldn't want to do any work in response to that!
Just to be
I asked this question on
SOhttp://stackoverflow.com/questions/7015097/best-practices-for-dealing-with-expensive-view-height-calculationa
month ago but got no answer. Maybe I'll have better luck here. :)
I keep running into a sizing and layout problem for custom views and I'm
wondering if
The new update process, where the apk and product details tabs operate
independently, is horrible. We updated our app by uploading a new apk,
clicking activate and then clicking save. We then updated the product
details and clicked save. Now the market shows all the details for the
update, but
On Sunday, August 14, 2011 7:00:43 PM UTC-4, TreKing wrote:
http://www.google.com/support/androidmarket/developer/bin/request.py?contact_type=publishing
Been there. Done that.
Good luck.
Indeed. To us all.
--
You received this message because you are subscribed to the Google
Groups
Well, it took the better part of two hours, but the updated .apk did finally
appear. What a harebrained way of doing things.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
The documentation for application
licensinghttp://developer.android.com/guide/publishing/licensing.html#server-response-codesdescribes
LICENSED_OLD_KEY as meaning:
The application is licensed to the user, but there is an updated application
version available that is signed with a different
In the docs on server response
extrashttp://developer.android.com/guide/publishing/licensing.html#extras,
I find this:
When network problems prevent or interrupt a license check, the Android
Market client notifies the application by returning a RETRY response code
to the Policy's
I have a rather involved requirement for a rather simple layout. I have an
activity with a single ListView floating in the middle of the screen with a
background margin of uniform width all around. So far no problem. Now I need
the margin to be as large as possible given the content of the
I thought I had addressed that. Assuming that the smaller margins are at
least the minimum, then the larger margins should shrink (the ListView
should expand in that dimension) until they are equal all around. I think
you are right that this cannot be done in XML alone, but I asked hoping that
Are there any downsides to using the same signing key for publishing
apps under different Android Market accounts? (Different apps under
each account.) Likewise, are there any problems in using different
signing keys for different apps in the same account? I would assume
not in both cases, but I
Good point about selling app ownership. I take it, then, that the only
issues have to do with key management (security; recovery; transfer)? The
market itself doesn't care what keys are used where?
--
You received this message because you are subscribed to the Google
Groups Android Developers
should file a
feature request (enhancement) at b.android.com if you'd like the tools to
keep these methods.
On Sun, May 1, 2011 at 6:55 PM, Ted Hopp ted.h...@gmail.com wrote:
Apparently proguard decides that it's an unused method because nothing
in my code references it, and optimizes it away
For every new project, I always have to add the following lines to
proguard.cfg:
-keepclassmembers class * extends android.app.Activity {
public void *(android.view.View);
}
Otherwise the onClick methods disappear when I publish the app. Is
there a way for us to change the default
Apparently proguard decides that it's an unused method because nothing
in my code references it, and optimizes it away.
On May 1, 9:10 pm, a a harvey.a...@gmail.com wrote:
2011/5/2 Ted Hopp ted.h...@gmail.com:
For every new project, I always have to add the following lines to
proguard.cfg
Thanks, Michael. We hadn't thought about the possible need to hand over the
signing keys. That's a good argument against using our usual key pair.
I'm a bit leery of publishing to one account and then asking the Google team
to switch the app to another account. I've read postings here and on
The Google Market team is very responsive to requests for transferring
your app to a different account.
Did the app use the licensing library? If so, I imagine that the process
wouldn't be quite so simple as asking the Google team to move it. Wouldn't
it involve a new .apk file that used the
Thanks, Kostya. I'm curious why the (public) publisher account key would
need to be obfuscated. What vulnerability would there be if the key were
publicly known?
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send
We have developed several apps and published them on Android Market. We are
now writing an app that another company will brand and sell through their
own publisher account. The other company has no experience with Android
Market or with Android development. I'd appreciate any insights from
Thanks, Chris. That seems obvious now that you point it out. :)
Is there any reason that they could not use an .apk file signed with our key
to publish to their Android Market account? Signing (and then running
zipalign) seems like the kind of work that should fall to us as the
developers,
The problem persists in 2.3.3 (API level 10) emulator, at least for
us.
On Feb 5, 11:36 am, Marcin Orlowski webnet.andr...@gmail.com wrote:
Same code works on version 2.2 of the Google API emulator, but not 2.3
of the Google API emulator.
It's known, confirmed
The new documentation on ProGuard (http://developer.android.com/guide/
developing/tools/proguard.html) says to add a line to the
default.properties file in the project home directory. However, on
opening this file, I read at the top:
# This file is automatically generated by Android Tools.
When I add a GZIPed file to my Android project's assets, the .gz
extension is stripped when the project is packaged in Eclipse. (So,
for instance, foo.gz in my assets folder needs to be accessed in
code using getAssets().open(foo).) This doesn't seem to happen with
other extensions (e.g., .html)
I'm given a large number of grayscale images in the form of byte arrays. I
want to use the values in each image as an alpha mask for drawing a solid
color in a Canvas. The images are fixed but the color changes. I can create
Bitmap objects for each image/color combination, but that seems
, Ted Hopp [EMAIL PROTECTED] wrote:
A couple of follow-up details. Turning off focusable in touch mode
(while undesirable for my app) fixes the scrolling problem...mostly.
Now, when I scroll in touch mode to a position where no focusable view
is visible it stays there. So far so good
If the data will only be accessed strictly within your application,
then extending Application is the easiest way to go. Otherwise the
Android way is to create a content provider. Storing transient data in
static variables is not reliable.
On Apr 8, 3:15 pm, Soonil Nagarkar [EMAIL PROTECTED]
.)
Thanks for any help with this!
Ted Hopp
--~--~-~--~~~---~--~~
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
You can call setConnectTimeout() before making the connection. If
there is no internet connection, the response code should be -1. (Note
that the default timeout is 0, which means that your connection will
wait forever for a response.)
Ted Hopp
On Mar 30, 7:17 am, aTai [EMAIL PROTECTED] wrote
With some searching I've found several examples and explanations of
customizing the look of a component based on the drawing states. But I
haven't found anything about defining custom drawing states. For
instance, suppose I have a component that maintains states that I
might call baked and fried
on the value of getNodeType() and cast
(or ignore) accordingly.
Ted Hopp
On Mar 30, 2:27 pm, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Hi!
I tried parsing an XML file which I had created through code. The file
has lines seperated by System.getProperty(line.seperator,). The
DOM engine parses
I read another thread here a few days ago that pointed out that an
Application object can be used as a central place for data shared
between activities. It seems to be working nicely for me. I don't use
it to pass data back from subactivites, but I imagine it would work
just as well.
However, in
46 matches
Mail list logo
