I believe Dianne gave you the answer....
Do you add the PackageManager.GET_META_DATA flag when you get the
applicationInfo ?
Sincerely,
Brad Gies
-----------------------------------------------------------------------
Bistro Bot - Bistro Blurb
http://bgies.com http://nocrappyapps.com
http://bistroblurb.com http://forcethetruth.com
http://ihottonight.com
-----------------------------------------------------------------------
Everything in moderation, including abstinence (paraphrased)
Every person is born with a brain... Those who use it well are the successful
happy ones - Brad Gies
Adversity can make or break you... It's your choice... Choose wisely - Brad Gies
Never doubt that a small group of thoughtful, committed people can
change the world. Indeed. It is the only thing that ever has - Margaret Mead
On 05/01/2011 9:43 PM, jesse wrote:
bump! any one has similar experience?
On Wed, Jan 5, 2011 at 12:20 AM, jesse<[email protected]> wrote:
According to this page:
http://developer.android.com/guide/topics/manifest/manifest-intro.html,
provider can have meta-data.
however, when I check providerInfo.metaData in attachInfo() function
of a derived provider class, it is always null?
is this a bug is android SDK 7?
public class MyProvider extends ContentProvider {
..
public void attachInfo(Context context, ProviderInfo info) {
super.attachInfo(context, info);
Bundle bundle2 = info.metaData;
However, bundle2 is always null here.
here is my manifest xml file:
<provider android:name="MyProvider" android:authorities="com.xxxx..MyProvider">
<meta-data android:name="varNme" android:value="xyzzxzxz" />
</provider>
thanks!
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
