Most straightforward tutorial on RUclips. Only issue I encountered was manual signing not validating for me, so I checked automatic signing and it worked.
I have the exact same issue. But automatic signing forces me to use the development cert instead of the distribution cert. That prevented me from moving forward, and I am basically stuck. Xcode 15.3 here.
Please make a video explaining the in app purchases process in iOS, there is no video out there explaining how to build and make it work on iOS. Thank you for your videos!
Nice! You guided us to the app store effortlessly, without us having to think about anything-just following you blindly, and it worked. Will you also make a video that complies with France's regulations?
I got stuck in the distribute app part. It says invalid signing when my every setting is the same as yours. Manual signing is buggy, or there's something I have overlooked. But I did exactly the same things as you did. (xCode 15.3)
@@MrMProgramming I missed out to add the provisioning profile inside of Unity's Player Settings -> Others. I managed to build after adding that back in. But there's still a problem. It doesn't detect my provisioning profile certificate as "Distribution" but "Development" instead. I had to manually switch it to "Distribution". But on building out the xCode project to xCode 15.3, it will give me a warning. I dunno if that's what caused the crash on my app launch afterwards.
there are not enough guides like this out there really appreciate you guys
Finally a simple step by step that actually work! Thanks for the great video!
Most straightforward tutorial on RUclips. Only issue I encountered was manual signing not validating for me, so I checked automatic signing and it worked.
I have the exact same issue. But automatic signing forces me to use the development cert instead of the distribution cert. That prevented me from moving forward, and I am basically stuck. Xcode 15.3 here.
@@Kiik-h9s That's odd. Did you figure it out?
Thank you very much for your very clear and easy-to-follow tutorial, it helped me a lot! I just submitted my app for review 😊
Glad it helped! Hope your app goes live soon!:)
Informative Video, Thank you This video helped me a lot.
Please make a video explaining the in app purchases process in iOS, there is no video out there explaining how to build and make it work on iOS. Thank you for your videos!
Thank you so much! This video helped me a lot.
Nice! You guided us to the app store effortlessly, without us having to think about anything-just following you blindly, and it worked. Will you also make a video that complies with France's regulations?
Thank you for the kind feedback! Regarding the France regulations...maybe, in the future;)
Fantastic - great work - hugely appreciated - thanx
Thank you! We glad it helped:)
Please make a video explaining the in app purchases
Thank you for your request! We will definitely keep this in mind for our future videos:)
Great Update!
please make video how to publish game without mac cloud build unity
this is a topic we would definitely like to explore in the future!
I got stuck in the distribute app part. It says invalid signing when my every setting is the same as yours. Manual signing is buggy, or there's something I have overlooked. But I did exactly the same things as you did. (xCode 15.3)
It's hard to tell what went wrong based on the information you provided. Please provide more detail
@@MrMProgramming I missed out to add the provisioning profile inside of Unity's Player Settings -> Others. I managed to build after adding that back in. But there's still a problem. It doesn't detect my provisioning profile certificate as "Distribution" but "Development" instead. I had to manually switch it to "Distribution". But on building out the xCode project to xCode 15.3, it will give me a warning. I dunno if that's what caused the crash on my app launch afterwards.
your website is missing an ssl certificate, which blocks the access on almost any browser (but chrome). please check it.
We didn't find any problem with the website. Could you please try again and let us know if the problem persists?