iOS Quick Start guide

General Feedback & Requests
, , , ,
1

Hi, I’m testing my project for iOS device, i have follow the guide

and after a few errors I find that the guide is a little non updated, in fact even it say has been review for version 4.9 I think it’s already old from version 4.6

any case I find a question here from 2015 march that solve my problem. but it will be useful an updated guide about how to prepare a project for iOS.

I know it’s something messy that no one will like to do, but something needed.

thanks for your help!!

2

Hi geverk.

From that page, do you recall on which steps (# 1 through 9) that you found the information to be outdated?

If it is only a few steps, this will help us to focus our efforts to update them.

Thanks

3

hi,

not sure what have a new way to be done, any case I’m talking about deploy it from windows

For sure the step 6 import your mobile provisioning, from version 4.7 is needed to be done from the project settings

I’m not sure if also to do the certificate and the other steps there is an alternative to the IPhonePackager. Just ask about if there is actually a more efficient way to do all that stuff.

Thanks!

4

Geverk,

Are you having trouble packaging or deploying your iOS projects from Windows while using a blueprint or a c++ project? Did you end up setting up ssh (rsync) or did you end up doing something entirely different.

Please include the link to the post that helped you resolve your problem.

Thanks!

5

Sorry , I have search in between many post but i can’t find the one I refer before. (any case that is not the problem)

After follow the guide I have problem fo both, package and deploy, because the guide ask you to import the certificates with the IPhonePackager, but actually is needed to be done inside the engine project settings/platforms/iOs

Now I know that, I have package properly no problems; it’s a full blueprint project.

So the iOS Quick Start guide is outdated, and I guess that have been a problem for many to star packaging for iOS as have been for me.

Thanks!

6

We’re working on getting our documentation updated. Thanks for the update!

7

Thanks for reporting the outdated documentation to us. I have entered a for this, which is referenced as: UEDOC-4055