Coronium IPv6

Third Party Coronium
#1

How is Coronium affected by Apple’s new IPv6 requirements?

#2

As far as I understand you are fine if you use the public dns of your EC2 instance instead of the public IP, with is in v4 format.

The new rule does not mean that IPv4 is not longer supported, instead it means that you have to make sure that IPv6 is definitely supported, what is not the case if you hardcode a IPv4 address.

#3

You can read how  to test your app for IPv6 compatibility here …

https://developer.apple.com/library/mac/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html#//apple_ref/doc/uid/TP40010220-CH213-SW1

#4

Thanks for the help. I’ve got a DigitalOcean droplet. I can transfer a host name there. And then, in the coronium:init( { appId = “xxx”}) string would i put the host name? And if so, formatted www.hostName or http://hostName? This bit is all pretty new to me… 

#5

I got it figured out. Thanks sunmils!

#6

I’d be curious to hear what you did Kevin. I’ve just put up a Coronium server on DO and I’d like to have it configured properly. Do I need to get a SSL cert and domain name for it?

#7

I configured the droplet with IPv6, straightforward instructions posted there. Then transferred a URL to that server. Then used the URL as the Coronium appId in the client. Works as expected. That said, I’m not sure it’s needed, at least to conform to Apple’s requirement, because the app passed it’s Ready For Sale review with the old IPv4 appId still in place…

#8

As far as I understand you are fine if you use the public dns of your EC2 instance instead of the public IP, with is in v4 format.

The new rule does not mean that IPv4 is not longer supported, instead it means that you have to make sure that IPv6 is definitely supported, what is not the case if you hardcode a IPv4 address.

#9

You can read how  to test your app for IPv6 compatibility here …

https://developer.apple.com/library/mac/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html#//apple_ref/doc/uid/TP40010220-CH213-SW1

#10

Thanks for the help. I’ve got a DigitalOcean droplet. I can transfer a host name there. And then, in the coronium:init( { appId = “xxx”}) string would i put the host name? And if so, formatted www.hostName or http://hostName? This bit is all pretty new to me… 

#11

I got it figured out. Thanks sunmils!

#12

I’d be curious to hear what you did Kevin. I’ve just put up a Coronium server on DO and I’d like to have it configured properly. Do I need to get a SSL cert and domain name for it?

#13

I configured the droplet with IPv6, straightforward instructions posted there. Then transferred a URL to that server. Then used the URL as the Coronium appId in the client. Works as expected. That said, I’m not sure it’s needed, at least to conform to Apple’s requirement, because the app passed it’s Ready For Sale review with the old IPv4 appId still in place…