Introduction:
The project was upgraded to 2019.4.x. When using jenkins to package, I found that using the previous process, both Android and iOS packaging would fail.
Changes to the packaging mechanism of the new version of Unity
In the Android gradle template, the Android project exported by Unity is no longer Application, but Library.
iOS is even more similar. When exporting the XCode project before, there was only one Unity-iPhone Target (not counting Test), and the XCode project exported by the new version of Unity, in addition to the original Unity-iPhone, there is also a UnityFramework .
The impression is that Unity tends to organize the exported projects into a library, and then use the entry project for references and dependencies.
Encounter problems
Because there was a code to automate the iOS package before, the library and dependencies had problems when the iOS package was printed. There is no problem when using the real machine to debug, just run it directly, but after submitting it to TestFlight, test it and go in. It flashed back, it was a headache.
After detection, it is found that the UnityFramework generated later is in the Dependencies of Unity-iPhone, but not in the static link library, so try to add UnityFramework to Link Binary With Libraries
Package testing, local real machine testing and TestFlight testing are all fine. problem solved