i've done simple map application.Here i got api key from debug.keystore .Its working fine on emulator.when i try to get it as apk file & run that on device.,it didnt display map.i think i need to create release key for that.How can i generate release key for that & how can i make my appn signed with that key.Anybody let me know the procedures for that.i used http://developer.android.com/guide/publishing/app-signing.html. But im not much clear.
You have to generate a key for the certficate you use to sign your .apk file. Look here to get step by step instructions on this.
Related
I am using the Demo company to develop.
The company expired so I re-activated it
However when I try to run my unit test to connect to a table I get the following error
Xero.Api.Infrastructure.Exceptions.UnauthorizedException:
oauth_problem=token_rejected&oauth_problem_advice=
The%20organisation%20for%20this%20access%20token%20is%20not%20active
I decided to try and regenerate the keys.
When I go to the App page in developer.xero.com and select the option to do this I get a question
Regenerate Keys?
Are you sure you want to regenerate your application keys?
This will break any instance of the application using the old key and secret.
I answer Yes, then an error appears briefly at the bottom of the screen in red.
Error! Please refresh
The dialog does not close.
The keys do not re-generate.
I am using Chrome as the browser on Win 10
Re-generating the demo organisation actually creates a whole new organisation; because of this, your app is still linked to an expired demo organisation, so it won't get new keys.
I think you'll need to create a new app to be able to use your new demo organisation.
In Titanium you can set and get data using:
Ti.App.Properties.setString("token", "")
A customer has an issue with a live app. I suspect it has something to do with how some of this data is set.
How can I find out what the values are for his phone? Where is it stored?
I assume it's in a file somewhere but where???
I'm not sure if it's possible to retrieve the local properties in the file system of the phone itself. And even if that's possible I assume that those keys / values are encrypted.
The thing I know is that Appcelerator uses pre-reserved keys in local properties. Meaning that every time you build your app the key will be overridden. I often, instead of general key names, use more descriptive key names like 'api_token' or something like that.
I'm not sure if this helps but another thing that you could try is to log the incoming token on the server end and evaluate from there.
I'd like to update to GCM 8.4 from 8.3, but part of the new process requires auto generation of a json file. I tried that with my existing project, but it created a new api key of type "Android" while the api key I was using before was of type "Server". Is it possible to use my existing "Server" key so that existing users continue getting push notifications? If so how am I supposed to go about doing so?
I can manually edit the json file, but I'm not sure how the old data I was using corresponds. The old information I have is the GCM_PROJECT_ID and a GCM_CLIENT_ID (same as project id except with some sort of hash and has "apps.googleusercontent.com").
Any help is appreciated.
I just cloned this repo from github and would like to have a play with it. However, in XCode, I keep getting the following error:
The identity '3rd Party Mac Developer Application' doesn't match any valid, non-expired certificate/private key pair in your keychains
It's worth noting that in my Build Settings, I've set the Code Signing Identity property to Don't Code Sign, but I'm still getting this error.
Has anyone ever encountered this, and if so, what did you do to fix it?
Thanks!
I have downloaded the project and noticed that there are 2 Xcode projects:
SpectttatorTest.xcodeproj,
Spectttator.xcodeproj.
The first one has set "Code Signing Identity" to "Don't Code Sign", but the second project (which is embedded in the first as a dependency) has set "Code Signing Identity" to "3rd Party Mac Developer Application".
After setting "Don't Code Sign" for the second project no code signing error occurred anymore.
Ater changing the setting, if you notice the same thing happening with your own projects, it may be time to get a new certificate. It's what I had to do last July.
EDIT:
If indeed that's what you have to do, this SO link contains an answer describing the procedure for moving forward.
So, I know just recently that google maps API is now available in SSL (here).
My question is, how do I retro-fit my http google maps api script to use this?
So my http Google maps API script call looks like this:
http://maps.google.com/maps?file=api&v=3&sensor=false&key=########
They suggest via this link that to use SSL it should be this:
https://maps-api-ssl.google.com/maps/api/js?v=3&sensor=false
I've tried retro-fitting this into my old URL format like so:
https://maps-api-ssl.google.com/maps/api/js?v=3&sensor=false&key=########
but that no longer displays the map.
Does anyone have any suggestions on what the URL should be?
Thanks
Try this line:
https://maps.google.com/maps/api/js?v=3.5&sensor=true
Google btw suggests that you explicitly enter what version of the api you are going to use. Just entering v=3 will always return the latest version, at the moment 3.5. I believe that the current stable version is 3.3.
As Trott wrote in his answer, api key is no longer needed.
You don't need an API key to use v3, but I suppose it probably doesn't hurt. General things to try:
Open your browser's JavaScript console and see if it is reporting any problems when you load the page.
Remove the API key
Change & to just &
Copy and paste the exact link text you put above into your code, because that link text is working for me. I'm referring to this:
https://maps-api-ssl.google.com/maps/api/js?v=3&sensor=false&key=########
Of course, change ######## to your API key (or just remove it altogether).