Atsushi
A follow on - I discovered a debug.keystore in the
users\me\appadata\local\xamarin folder which was dated 20/08/2011 which when
used to generate a fingerprint had a validity out to 2040
But even this new fingerprint is giving invalid code on both Google api V1
and V2 console
I am using SHA
Scenario what i'm trying to achieve:
1. Loading activity with two frame containers (for list of items and for
details).
2. At the app launch time add listFragment in listFrame and some initial
infoFragment in detailsFrame containers.
3. Navigating through list items without adding each detail trans
Are you seeing any "permission denied" messages in the console while your
application is running?
Another wild guess:
Are you sure that the debug.keystore you are using to sign the app is the
same one that you associated with the API Map Key? You can check out the
SHA1 fingerprint of your APK by f
On Sep 6, 2012, at 4:03 PM, ghuoof wrote:
> I'm having a similar problem and I'm completely stumped. At this point I am
> just trying to do some very simple stuff with fragments.
The problem is a type name mismatch; your fragment uses the class
`com.goctsi.com.oti.eventslistfragment` (note the
This occurs if I install the app through Visual Studio or if I use a 3rd
party installer.
I haven't tested yet but I'm hoping it doesn't happen when downloaded from
App Store.
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Confusing-Main-Launcher-Icon-Behavior-t
Hi I am reading this for the first time and wondering if anything has changed
in the past year.
You wrote, "Unfortunately we don't have a good answer at this time."
Is that still the case or has the situation improved? Thanks.
--
View this message in context:
http://mono-for-android.1047100.