IPv6 & Apple

Charles Warwick charles at techstrategies.com.au
Tue Aug 23 00:27:54 EDT 2016

Hi Scott,

Ok, there are a couple of issues there.

Using "" as tDatabaseAddress indicates you are using a 
hardcoded IPv4 address which can cause problems.

However there is a bigger issue there in that the database library in LC 
does not support IPv6.

This means that for iOS apps that you want to submit to the app store, 
you cannot directly connect to a remote database server using LC's 
built-in database library.

The best solution I can recommend would be to use a HTTPS API written in 
either LC, PHP, or something else to sit between your LC app and the 
database server.

This also gives the added benefit of not needing to leave your database 
server open to connections from anywhere on the Internet.

Feel free to contact me off-list if you want some more specific 



On 23/08/2016 2:02 pm, Scott Rossi wrote:
> Hi Charles:
> The app makes database calls using the following structure.
> put "" into tDatabaseAddress
>     put "dbname_" into tDatabaseName
>     put "dbuser" into tDatabaseUser
>     put "dbpassword" into tDatabasePassword
>     put revOpenDatabase("MySQL", tDatabaseAddress, tDatabaseName,
> tDatabaseUser, tDatabasePassword) into tResult
> I have ATS disabled in the standalone because we don't currently have an
> HTTPS server. The error displayed in Apple's screenshot was my simple
> error message stating it was unable to connect to the database.  I need to
> go back now and figure out if there's some missed issue with the code.
> But it concerns me if Apple is testing the app in some way that I don't
> have a means to reproduce.  I'm not very knowledgable in server matters so
> any advice is appreciated.
> Thanks & Regards,
> Scott Rossi
> Creative Director
> Tactile Media, UX/UI Design
> On 8/22/16, 8:22 PM, "use-livecode on behalf of Charles Warwick"
> <use-livecode-bounces at lists.runrev.com on behalf of
> charles at techstrategies.com.au> wrote:
>> Hi Scott,
>> On 23/08/2016 7:07 am, Scott Rossi wrote:
>>> Does anyone have any experience with this?  The backend database guy I'm
>>> working with thinks this is a hosting issue (host needs to support
>>> IPv6).
>>> Will switching to a host that supports the new protocol allow us to
>>> troubleshoot/fix this?
>> You do not require a server that supports IPv6 to resolve the issue.
>> Apple are only enforcing that the client app works on a device that is
>> operating on a IPv6 only network, not that the app only connects to IPv6
>> servers.  Your app can still connect to IPv4 networks, as the IPv6 only
>> network provider will have DNS64/NAT64 translation in place for
>> connecting to IPv4 networks.
>> The problem will usually be because you are using hard-coded IPv4 IP
>> addresses rather than relying on DNS to resolve any hostnames, or that
>> you are using some networking component that doesn't support IPv6 in
>> your app.  What sort of network calls are you making from your app, are
>> they only HTTP/HTTPS?
>> Regards,
>> Charles
>>> Thanks & Regards,
>>> Scott Rossi
>>> Creative Director
>>> Tactile Media, UX/UI Design
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

More information about the Use-livecode mailing list