[stefinos]

Hi guys,
Even I really like your MobiOne software, there is a serious issue, if you use the website links.
If a mobile phone does not have internet access, the app does only say ‘failed’.

I am using popup window (full control)

Apple:
If your app requires the use of the Internet, you must detect when the network is unavailable and provide a pop-up message informing the user. Just having the spinning busy icon display and a message saying “failed” is not sufficient.

Can you Genuitec guys fix this urgently?

Cheers, Steffen

[WaylandDavis]

Doesn’t Apache Cordova (PhoneGap) 2.2 support a Connection. Telling you whether you have 3G, 4G, Wifi, Ethernet, etc?

I would think this would suffice. If you don’t have one of these, then you can’t get on the internet…It also tells you if you have no connection and you can pop up an alert.

[stefinos]

Hi, thanks for your response, but it does not answer the question or solves the issue.
Just to be clear:

1.I am using MobiOne Vers. 2.3.0 to develop a native app for IPhones
2.Using a botton or text field
3.Using Properties > Action > Go To URL
4. Popup window (Full Control)

If the Iphone has not internet connection, the MobiOne app just says ‘failed’

Apple rejects your native app. – You cannot publish in the Apple Store.

The Property action Go To URL must com back with a message ‘No internet connection’.
At the moment you just get ‘Failed’

Hopefully Genuitec can fix the issue.

Cheers

[Unknown Author]

Well, that’s odd.

A few days ago, Apple approved my iOS app update with two weblinks exactly like what you’re describing.

-1TC

[WaylandDavis]

Stefinos,

I tested this code with my iPhone 4S running 6.01 and 2.3.0 Mobione. First thing that happens when the phone comes up is it checks the phone connection. If you don’t have a connection, it tells you that there is ‘No connection.’ If you do have a connection, it tells you the type (i.e., wifi, 3G, 4G, etc.)

It does not work in test center, only on the device itself, so you have to add it into your APPNAME_custom.JS file.

Try it. Maybe it’ll help…

phoneui.documentReadyHandler = function()
{
document.addEventListener(“deviceready”, onDeviceReady, false); [/color]

}

function onDeviceReady()
{
checkConnection(); // Go and see if you have an internet connection before you push the GotoUrl button.
}

function checkConnection()
{
var networkState = navigator.connection.type;
var states = {};
states[Connection.UNKNOWN] = ‘Unknown connection’;
states[Connection.ETHERNET] = ‘Ethernet connection’;
states[Connection.WIFI] = ‘WiFi connection’;
states[Connection.CELL_2G] = ‘Cell 2G connection’;
states[Connection.CELL_3G] = ‘Cell 3G connection’;
states[Connection.CELL_4G] = ‘Cell 4G connection’;
states[Connection.NONE] = ‘No network connection’;

alert(‘Connection type: ‘ + states[networkState]);

// Here you could disable the button if the state was No network connection or Unknown connection so they
// wouldn’t be able to push the “Go to Url” button.

}

[support-michael]

all: this is a good topic for discussion.

@wildwex
I use a similar network check as you posted that has served my purposes well.

I chatted with the dev team about graceful failure of actions that require a network connection but it is not available at runtime, e.g., gotoURL with remote URL. My understanding why network checking is not built into phoneui.js atm is the unreliability of detecting if the device is actually connected to the internet. My understanding is the api’s can only identify if the device’s network interface is active which is not the same as an internet connection. There are also other ways of failure that are hard to detect and have potential for false negatives, i.e., app tells user he does not have a network connection when in fact the device does or vice versa. This is why the current internet specific actions lack a standard network error reporting.

We have a followup discussion on this topic planned tomorrow. I am hoping we can provide more automated checks in near future – no promises.

[Tulsaboy]

Reading this just now is quite a shock to me. I have spent the last couple months making a couple apps that are heavily dependent on web pages, and was thinking they were ready to release. Until now I had no idea there could be any problem building them with MobiOne and getting them approved. It seems odd that this would not have surfaced before. Or is Apple maybe getting stricter lately?

Unfortunately, I have no experience with Javascript, etc., and was depending on just using the basic MobiOne program. If there are ways to take care of this with extra programming, and if Apple is now starting to consistently do this, no doubt I will need some help. If Genuitec does not come up with a solution soon, then I expect I may need to hire someone to help me on this specific issue. (That is, of course, if there is a work-around possible.) Any advice would be appreciated. You can contact me by email: dean at bevio.com

Thanks!

[Unknown Author]

Has anyone here actually had their app rejected because of this issue?

I had my app update approved no problem, using the same in-app weblink. Exactly what you’re saying is a major issue was no issue at all for me.

-1TC

[StudioCarinci]

For 2 or 3 web link on an app, Apple approve it with no problem but if you have an app with large based web links Apple doesn’t approve it. I tried 3 times and nothing 🙁

[support-octavio]

@all,

We plan to use this info in a faq for appstore appoval issues.

[stefinos]

With all due respect for apple products and software, but this issue with the weblinks in an apple app really
bothers me. There are many exceptions where apple approves iOS apps with 1000 of weblinks in an app.
Best example is “yellow pages” in New Zealand. They have a website link almost for each listing. And it got approved by apple!

[Brandon]

It seems the problem isnt with the number of weblinks, its what else the app offers. The way Apple explained it to me is if you are only opening a bunch of links they can use the built in Safari browser for that.

They are getting really strict on the checking for connection issue though.

[Unknown Author]

That explains why my app update was approved; two web links on one page. No weblinks on the other 150+ pages of content.

[support-michael]

@CincyPlanet
>It seems the problem isnt with the number of weblinks, its what else the app offers. The way Apple explained it to me is if you are only opening a bunch of links they can use the built in Safari browser for that.

You are spot on. Apple’s view is your app must provide an obvious value to be worthy of inclusion in the appstore. That is a very subjective statement but apple is pretty firm about restricting webapps disguised as an app from the appstore.

[Paul_paul]

If you have that many “gotoUrl” you might just as well have a mobile enabled website, don’t see the point of an app if it’s totally internet dependent. Kinda defeats the purpose. None of my apps rely on an internet connection to function other than for the initial download.

[Author]

Posts