Accept self-signed SSL certificate

12 posts, 0 answers
  1. Max
    Max avatar
    11 posts
    Member since:
    Jan 2013

    Posted 17 Apr 2013 Link to this post

    I have a REST service with a self-signed SSL certificate. My app is able to make successful API requests with the simulator. I would like to be able to test on my Android device, but all my requests are failing. Any suggestions?
  2. Max
    Max avatar
    11 posts
    Member since:
    Jan 2013

    Posted 17 Apr 2013 Link to this post

    I found this post which suggests editing the manifest.

    http://stackoverflow.com/questions/8977226/phonegap-ajax-call-to-https-server-with-self-signed-certificate-fails

    How do I go about doing that with Icenium?
  3. Jan-Dirk
    Jan-Dirk avatar
    327 posts
    Member since:
    Jun 2012

    Posted 18 Apr 2013 Link to this post

    Something I ran into in the past and that comes to mind is something that is called NAT loopback.

    'This means that a machine on your local network (e.g. behind your DSL
    router/modem) cannot connect to a forward facing IP address (such as
    199.149.252.44) of a machine that it also on your local network.
    Connecting to the local IP address (such as 192.168.2.40) of that same
    machine works fine.'

    If you have had to configure the host file in the past on your PC (and now forgot about it), then this is probably your problem. You can't change the hosts file on your Android device (unless the device has been rooted), but what you could do is setting up a proxy.

    I hope this helps.

    Off topic: I would love to see a nice example of using REST services and SSL with Cordova. If you have time, please consider to post an example in the 'show your code' forum.
  4. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 18 Apr 2013 Link to this post

    Hello Max,

    You can control whether you're in Debug or Release from the Build Settings. Right-click the first node in the Project Navigator, choose Build Settings and alter the "Active Build Configuration" as you need. The default one (empty) is Debug.

    Kind regards,
    Steve
    the Telerik team

    Share feedback and vote for features on our Feedback Portal.
    Want some Kendo UI online training - head over to Kendo UI Dojo.
  5. Max
    Max avatar
    11 posts
    Member since:
    Jan 2013

    Posted 18 Apr 2013 Link to this post

    Steve - I see what you are talking about and I can switch between debug & release modes. But I don't see where I would be able to edit the configuration...

    Jan-Dirk - good thought. I actually have already taken care of the loopback though. Besides which, it fails whether I use my local network or if I'm off site.
  6. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 18 Apr 2013 Link to this post

    Hi,

    The post you referred to talks about android:debuggable which is controlled by the Build Settings explained in my previous post i.e. this setting controls whether android:debuggable is true or false in the AndroidManifest.xml file. You do not need to edit anything manually for this to happen.

    Kind regards,
    Steve
    the Telerik team

    Share feedback and vote for features on our Feedback Portal.
    Want some Kendo UI online training - head over to Kendo UI Dojo.
  7. Max
    Max avatar
    11 posts
    Member since:
    Jan 2013

    Posted 18 Apr 2013 Link to this post

    Oh, excellent. Thanks. How would I change the setting in Mist? I need to use the QR code with remote build refresh.
  8. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 18 Apr 2013 Link to this post

    Sorry for the misunderstanding Max, it seems I was wrong. The debug/release settings implied the behavior of adding debug to the AndroidManifest.xml file, but we actually use it only to specify whether we would be using livesync (and insert Icenium-specific bits to your app's binary) or not.
    At this time, Icenium does not expose the AndroidManifest.xml for editing. We plan to enable this functionality in one of our next updates of the product. Till then you can manually edit this file from the compiled apk file as discussed in this forum thread.

    Kind regards,
    Steve
    the Telerik team

    Share feedback and vote for features on our Feedback Portal.
    Want some Kendo UI online training - head over to Kendo UI Dojo.
  9. Max
    Max avatar
    11 posts
    Member since:
    Jan 2013

    Posted 18 Apr 2013 Link to this post

    Ok. Thanks.
  10. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 05 Jul 2013 Link to this post

    Hi Max,

    You no longer need to disassemble and re-assign manually your apps in order to make a configuration change. In Icenium 1.6 we've added the ability to make configuration changes to your app by modifying the respective Info.plist and config.xml for iOS and AndroidManifest.xml and config.xml for Android directly in the Icenium code editor. For more information, see Edit Configuration Files.

    Regards,
    Steve
    Telerik

    Looking for tips & tricks directly from the Icenium team? Check out our blog!
    Missed our first webinar, watch it here.
    Share feedback and vote for features on our Feedback Portal.
  11. Eyecasa
    Eyecasa avatar
    1 posts
    Member since:
    Dec 2013

    Posted 30 Jan 2014 in reply to Steve Link to this post

    Steve... 
    I just try what You suggested... and it appears "changing to Release" using GRAPHITE is broken !!!

    I changed from DEBUG to RELEASE, then BUILD again... but the GOOGLE Apps site say  CODE IS STILL BUILD IN DEBUG mode.
    I moved to the new Telerik IN BROWSER CLIENT and BUILD for publishing to Google, and THIS DOES THE TRICK 
  12. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 31 Jan 2014 Link to this post

    Hello Eyecasa,

    We currently have such problem in the Visual Studio extension for AppBuilder, but it does not seem to be true for AppBuilder for Windows client.
    If the problem persists, in order to help you further, we would need session logs from FiddlerCap (with the Decrypt HTTPS Traffic option enabled). Start it prior AppBuilder and save the HTTP requests to disk. Zip the sessions and upload them to a free file share site and give us the link here or alternatively open a support ticket and attach it in the ticket.

    Regards,
    Steve
    Telerik
    Icenium is now Telerik AppBuilder, and is part of the Telerik Platform. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)
Back to Top