[Solved] Can't build application with new version of plugin

[Karpov]

Hi!

I just update my TouchId plugin to the newest version (https://github.com/EddyVerbruggen/cordova-plugin-touch-id), because I need to check FaceId availability. But now I can't build the application. The error is below. I think the problem is on build server side. Is the build server support Xcode?

Error: [xcode-build] /tmp/builds/eMHPT9FzprhoGJRaWQ/app/Plugins/cordova-plugin-touch-id-3.3.1/src/ios/TouchID.m:26:11<br>unexpected '@' in program<br>      if (@available(iOS 11.0, *)) {

[Karpov]

[quote]Karpov said:

Is the build server support Xcode?

[/quote]

 

I mean "Is the build server support Xcode 9?".

And also, is the build server use iOS SDK version 11?

[Dimitar Kerezov]

Hello Karpov,

The build infrastructure for the Cordova 6.4.0 set is comprised of Xcode 8.1 machines with iOS SDK version 10. Due to the discontinuation of Telerik Platform, currently, we do not plan to upgrade our build machines to a newer version of Xcode.

Having said that, should you need to use the cordova-plugin-touch-id, I suggest installing the latest version of the verified plugin Touch ID. You can find more information about installing verified plugin in the official documentation.

Please, let me know if this helps.

Regards,
Dimitar Kerezov
Progress Telerik
Telerik Platform is retiring on May 10, 2018. This requires some actions on your side, so please consider reading the full announcement and migration guides at first opportunity.

[Karpov]

 

Hi! Thank's for the answer.

Unfortunately,  the latest version of the verified plugin Touch ID hasn't FaceId support.

[Garo]

Hello Karpov,

You are correct and the Verified Touch ID plugin does not have support for FaceId. This is the main reason why it works in AppBuilder and the original one does not. The FaceId functionality requires Xcode 9 and as my colleague Dimitar has mentioned in the previous response, we are still using (and will continue to do so until the Telerik Platform shutdown) Xcode 8.x on our build machines.

Having said that, I am sorry to say that it is not possible to gain access to the FaceId functionality while building an app in AppBuilder.

Regards,
Garo
Progress Telerik
Telerik Platform is retiring on May 10, 2018. This requires some actions on your side, so please consider reading the full announcement and migration guides at first opportunity.

[Karpov]

Hi! Thanks for the answer!

And what about supporting fullscreen mode for iPhone X?

My application has black areas at the top and bottom and a cant removes them because don't know how to add with the correct size for iPhone X.

[Dimitar Kerezov]

Hello Karpov,

I came across this stack overflow thread, which might help resolve the issue. Can you please check if one of the solutions suggested there resolves the issue?

Please, let me know if it was helpful.

Regards,
Dimitar Kerezov
Progress Telerik
Telerik Platform is retiring on May 10, 2018. This requires some actions on your side, so please consider reading the full announcement and migration guides at first opportunity.

[Karpov]

Hi! Only first part of the solution from  work, the second part doesn't work. When I add next code to my ios config.xml

<splash src="res/screen/ios/Default@2x~iphone~anyany.png" />
<splash src="res/screen/ios/Default@2x~iphone~comany.png" />
<splash src="res/screen/ios/Default@2x~iphone~comcom.png" />
<splash src="res/screen/ios/Default@3x~iphone~anyany.png" />
<splash src="res/screen/ios/Default@3x~iphone~anycom.png" />
<splash src="res/screen/ios/Default@3x~iphone~comany.png" />
<splash src="res/screen/ios/Default@2x~ipad~anyany.png" />
<splash src="res/screen/ios/Default@2x~ipad~comany.png" />

 

nothing happened. (Of course, I also add splash screen images )

[Dimitar Kerezov]

Hi Karpov,

Cordova's webview takes up a part of the screen based on the splash screen shown beforehand. This means that in order to display your app on full screen you would need a splashscreen, matching the iPhone X' screen size. As you currently do not have one, the iPhone X device defaults to what is available, which is a smaller image, resulting in the issue you are describing. In AppBuilder, adding additional splash screen images would mean the following:

1. Generate two images that will be used as splash screens for the iPhone X and place them in your application's App_Resources/iOS directory.  The images should be:
1. For portrait view - an image sized 1125 x 2436 px, named [e-mail]
2. For landscape view - an image sized 2436 x 1125 px, named [e-mail]
2. Open your project's Info.plist file for editing. Locate the following line:
   

   <key>UILaunchImages</key>

   and edit it in order to add the two new values so that it becomes something like this:
   

   <key>UILaunchImages</key>
       <array>
           <dict>
               <key>UILaunchImageMinimumOSVersion</key>
               <string>8.0</string>
               <key>UILaunchImageName</key>
               <string>Default-812h</string>
               <key>UILaunchImageOrientation</key>
               <string>Portrait</string>
               <key>UILaunchImageSize</key>
               <string>{375, 812}</string>
           </dict>
           <dict>
               <key>UILaunchImageMinimumOSVersion</key>
               <string>8.0</string>
               <key>UILaunchImageName</key>
               <string>Default-Landscape-812h</string>
               <key>UILaunchImageOrientation</key>
               <string>Landscape</string>
               <key>UILaunchImageSize</key>
               <string>{375, 812}</string>
           </dict>
   
           ... Other UILaunchImageName entries ...
       </array>

This would instruct the iPhone X device to use the images you created in step 1. which should in turn resolve the issue you are describing.
You can read more about how to edit your Info.plist configuration file in AppBuilder's official documentation. You can find a nifty guide to all splash screen sizes here.

Please, let me know if this helps.

Regards,
Dimitar Kerezov
Progress Telerik
Telerik Platform is retiring on May 10, 2018. This requires some actions on your side, so please consider reading the full announcement and migration guides at first opportunity.