Tuesday, June 18, 2013

Posting your first app onto playstore? Here's the list of things that you need to do



By default, apps developed are signed in debug mode by a special debug key. This is not allowed when uploading the application to playstore. You need to sign your apk before uploading to the playstore. Information related to signing process can be found here. This points to the Android developer link which has extensive information.

If you are running short of time and want to quickly finish off generating the key and signing your app, then you could head straight to here.

Once you have the keys ready, the next step will be generate a signed APK. If you are using eclipse then the information is available here but if you are using Android Studio, you might have a tough time finding the information. The screenshot on the right is self explanatory.

Once you have a signed apk ready, you can upload the same to the playstore site. There are little other things that you need to take care of, like the screenshots, application icon. I don't think those need an explanation. Everything else is self explanatory on the playstore.

Happy Publishing your app to the playstore.


Saturday, May 18, 2013

"open with" duplicate entries


             Just finished my first year using a MacBook Pro. Frankly I didn't learn much of the tips & tricks that one would have learned when working with Windows. If only my office migrated to Mac OS and my circles moved on from Windows to Mac OS, then I would have had a different story to tell here. Observed that Mac OS users are quite reluctant in providing any assistance. Users that I have met in person spend an extra-ordinary amount of their energy and time cursing the Windows rather than focusing on increasing the Mac OS user base. They need to focus their energy towards answering queries that new bies will have. Create a local forum for assistance/discussions would have definitely helped.

New MBP users might have faced the issue shown in the image. This would have happened when you keep installing updates to existing software. Over a period of time it gets really messy and that's when usually we start to look out for solutions starting with the easy ones first.

I pinged a Mac OS user I knew in person over twitter. Never got a response. Pinged him over email with a screenshot. Nope, no response again. See, that's that I was talking about.

Google for solutions, tadaaaa...get my answers in the first 2-3 links. Now with all this Google & Apple drama happening, the stubborn attitude exhibited by the MacOS users I requested for help are inadvertently helping Google make money. I bet not all MacOs users are the same but hey...stop the shit of cursing Android, Windows. Focus your energies where its needed.

Coming to the solution of the issue that I have been seeing. Running the below command on the terminal would fix the issue. This isn't a permanent fix but a temporary one which would do for me for a long time.

/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user