Eclipse 101: Debug Certificate expired on x/xx/xx xx:xx AM/PM

I'm new to eclipse IDE and when I tested my newly created app for android, I encountered an error "Debug Certificate expired on 6/1/11 10:51 AM".

Developers might encounter this error when using eclipse and what we need to do here is to remove the debug certificate file for eclipse to create a new one.

To do this in linux or mac os, go to your terminal then execute the command below. Make sure you have the proper access to remove the file.

rm ~/.android/debug.keystore


Hope this helps a lot of developers which are new to eclipse IDE. Thank you for reading.

Eclipse 101: ERROR: Failed to fetch URL https://dl-ssl.google.com/android/repository/repository.xml, reason: Unknown Host http://xxx.xxx.xxx.x

While doing an update on my Eclipse SDK for Android development, I came to a problem that I can't able to update SDK due to proxy problem which I didn't remember setting it up.

Problem is that I encountered this error "ERROR: Failed to fetch URL https://dl-ssl.google.com/android/repository/repository.xml, reason: Unknown Host http://192.168.101.5".

I tried disabling the proxy settings of Eclipse Network Connections in all active provider: Direct, Manual, and Native but nothing works for me and error still persist.

It took me half a day to figure out the problem is, and then I found the config file on Android for the proxy settings.

You just have to go to this path: ~/.android/androidtool.cfg.. and you will see the settings like on this below.

### Settings for Android Tool
#Tue Jun 22 09:08:34 PHT 2010
http.proxyPort=80
sdkman.monitor.density=72
http.proxyHost=http\://192.168.101.5
sdkman.show.update.only=false
sdkman.ask.adb.restart=false
sdkman.force.http=false


Then update it to remove the proxy port, proxy host, and set the force http to true. The settings should be like this.

### Settings for Android Tool
#Tue Jun 22 09:08:34 PHT 2010
http.proxyPort=
sdkman.monitor.density=72
http.proxyHost=
sdkman.show.update.only=false
sdkman.ask.adb.restart=false
sdkman.force.http=true


Thank you for reading this post. Hope it helps!

IE7 Error: Expected identifier, string or number

Most developers are suffering from IE7 compatibility issue. Most of the time, we encounters error when doing javascript. One of the error I encountered was "Expected identifier, string or number".

This error is due to IE expecting a data. For the sake of this post, I will use the jcarousel plugin passing the parameters we need.

<script type="text/javascript">
$(document).ready(function() {
    $(".carousel").jCarouselLite({
        visible: 3,
        btnPrev: 'a.prevbtnHome',
        btnNext: 'a.nextbtnHome',
    });
});
</script>

As you can see on the sample JS above, we are passing parameters ending all with comma ",". This approach will actually work on most browsers but not on IE7 and below.

To resolve this, you just need to remove the comma "," on the last parameter.

<script type="text/javascript">
$(document).ready(function() {
    $(".carousel").jCarouselLite({
        visible: 3,
        btnPrev: 'a.prevbtnHome',
        btnNext: 'a.nextbtnHome'
    });
});
</script>

Hope this post helps a lot!

Resolution to NuSOAP XML Parsing Error: XML or text declaration not at start of entity..

As I was doing a web service using NuSOAP in PHP, I encountered an XML Parsing Error saying "XML or text declaration not at start of entity.."

I re-checked my code multiple times but can't find any syntax problem.

I tried searching in google to find answers, but most of the forums are saying about the trailing spaces in the XML format which I believe I don't have.

Given that, I have NO CHOICE but to find it by myself..

After a long trial and error, doing some changes in the script.., removing some extra spaces.., replacing special characters.., removing some extra lines.., etc...

I was able to reach the end of the script and saw the new line after the PHP end tag "?>"..

Still in doubt, but I tried removing it.. and guess what?? it works!! That is a proof that patience and perseverance really works.. hehehe!!

Anyway, I can't believe that NuSOAP missed this.. Hope that their next version was able to resolve this..