ACTION_PACKAGE_REMOVED (or We just deleted 42.)

by Dianne Hackborn » Thu, 25 Feb 2010 10:38:55 GMT


Sponsored Links
 The data has the package name.




>



ACTION_PACKAGE_REMOVED (or We just deleted 42.)

by laphroaig15 » Thu, 25 Feb 2010 13:48:01 GMT


 Ah, I see.  The event is useful.  However, even with the package name,
at that late state, I still couldn't retrieve the app's meta data
bundle from the package manager, correct?  I tried to pull the
packages by uid and they had been deleted.  I assume that the app and
pkg infos are gone as well.  I've already built a registry now, but
I'm still curious.

thanks,

Jess




> >


Sponsored Links


Other Threads

1. Problem updating app in android market.

I have an application in the market and I tried to post an update, but
it says that "The apk must be signed with at least one certificate in
common with the previous version."  I don't have the previous
certificate and I can't simply create a new project since my app is a
paid app and I don't want to have users charged again.  What can I do?
--~--~---------~--~----~------------~-------~--~----~

2. Android should provide remote database access for applications...

Naturally, you've got the "right" idea - and the elements are (almost)
in place today. There's probably more legwork needed than a nicely
wrapped framework would require, and there's a security concern that
you need to cover yourself. What can be done today:
- On the server side, you can use AppEngine to build a RESTful web
server with a database back end. Authentication through Google
Accounts. Bonus for using AppEngine: The user authentication is
encrypted (SSL), right out of the box.
- The aforementioned user authentication is integrated in the user
facing part of the web server that you build. After logging on, it
allows the user to check and manage his or her stored data
- On the client side, use GET and POST methods to query the server
(could be SOAP or something else, of course), based on the protocol
that you implement. Most likely candidate is a XML-based protocol, I
suppose. Where it's getting shaky as of today: The part where you
access the implicit user authentication on the device. This is not
covered by the Android SDK, and the solution currently is through a
framework JAR that you download independent from the SDK.
- At any rate, to comfort both users and dev, you do not gain or need
access to user passwords, neither on the client, nor on the server
side.
- The downside as mentioned above, is the lacking formal integration
of user account lookups in the SDK. As an added challenge, the user's
gmail ID needs to directly travel along with every GET and POST call
from the client side, or initially at least, if the protocol you
implement has some form of session management. This is needed in order
to allow the selection of the user's data in the backend database. The
onus of encrypting the user's identifying information as part of your
protocol is on you!
JP






--~--~---------~--~----~------------~-------~--~----~

3. Tab Formatting

4. Review Sebelum Pre-Order Dibuka :)

5. pertanyaan seputar magi

6. Android should provide remote database access for applications..

7. How To Programmatically Turn On/Off WIFI?