problem generating iOS app for version 4.4.0 #1326
Comments
|
Upgrade your XCode |
|
Which version of XCode do we need for v-4.4.0? |
|
Just install the latest |
|
I'm using XCode 13.0 which should be supported. I've had this same issue on other versions as well for example: Are you by any chance compiling the plugin on XCode 12? If so, could you compile with XCode 13? Looking at the issue below it looks like this is the case for us as well: Note: the only thing inside of the application I'm trying to generate is cordova-background-geolocation-lt |
|
Hi! Hope you had a good New Years eve! This is a friendly reminder. It seems if the plug-in were to be compiled using Xcode 13, the issue could very well be resolved. Could you provide us with such a version? |
|
Hi, I have the same issue. Could you help us please? |
|
Hi @christocracy, We have the same problem and we also have a support subscription. Do I have to create a separate issue for our problem? or do you want to help us? |
|
What version of XCode are you using? |
|
XCode 13.0 like @CreetionMotia |
|
There's no way around it. You must upgrade XCode. The latest version of the plugin was compiled with XCode 13.2. In the near future, the plugin will be compiled with XCode 13.3. |
|
Which release version is compiled with xcode 13.0? |
|
I don't keep track of that. |
|
@CreetionMotia and @christocracy . |
|
@CreetionMotia from outsystems support I got the following message today; We wanted to inform you that we'll be shipping XCode 13.3 with MABS 8.1. The Beta will be updated next Wednesday with some fixes and it will include XCode 13.3. I hope that at least version 4.2 of the plugin will work with an Outsystems mobile application. |
|
Hello @christocracy , I have tried to build our application with MABS 8.1 with the following versions;
Android is build successfully, but we still getting the following errors for iOS; [2022-04-14T09:09:50.803Z] [VERBOSE] [Build] Undefined symbols for architecture arm64: What is wrong? |
What is "MABS"? |
|
MABS is the Mobile Apps Build Service of Outsystems. |
|
I do not know why your build system is having problems. It seems to have trouble importing the The latest Cordova CLI is I do not have any issue building on my local machine. |
|
Hi I have the same problem, I used the plugin in OutSystems application for almost two years, but now with the last versions I can't do it anymore. @Furkan68 or @CreetionMotia any update about that? I start another application in OutSystems for another customer that bought the plugin by my advise and now I can't use it inside the application. This is the last answser that I have from my support team: Thank you for your time during our call. As discussed, we analyzed the iOS build logs from MABS and we found the following error being thrown. From similar support cases, this issue is caused by the unsupported "https://github.com/transistorsoft/cordova-background-geolocation-lt" plugin. This is also a known issue of this plugin as you can see on this forum, #1326. We tested using this plugin in a sample application and were able to replicate the error using the plugin latest version and MABS versions 8.1.4 and 7.2. When removing the plugin the build is successful so we can conclude that the bottleneck is the "https://github.com/transistorsoft/cordova-background-geolocation-lt" plugin. From the git forum it seems that a possible workaround would be to use version 3.7.0 with MABS 7.2. We tried to test this workaround in the created sample application but with no success. It always throws the error below when fetching the plugin version 3.7.0. Maybe it is related with the license of the plugin, we are not sure. From the above findings and troubleshoot perform and since this is not a supported component we can only suggest the following: As agreed during our call, since there are no more actions items on our side we will be marking this case as solved. @christocracy can you help me, please? |
|
3rd party build systems always have old tooling. Nobody has a problem building locally. |
|
And OutSystems is particularly horrible. I’ve recommended people avoid them for years. |
|
Hi @christocracy thanks for your answer but I think this is not the problem, for some reason the tool can't download the application anymore. Is there any problem with my license? If I tried to download version 3.7.0 to keek the compatibility I can't and I don't know why. And the problem here is the opposite, because OutSystems update your MABS tool I was forced to recompile that application. OutSystems it's the biggest company in the world in your market, bigger than Microsoft in Low Code market. I developed I integration with your plugin so I believe it's an excellent market for your plugin regardless of your opinion about the platform. You don't become the greatest in the world by being horrible.But regardless of our opinions, can you help me understand what is happening and how to solve it? Because in the end what MABs do is compile on a local machine. What more information can I give to try to resolve it? Can I request all local MABs configuration eg detailed log and etc. Thanks in advance. |
|
iOS is free, it doesn’t consume license keys. only Android consumes license keys. |
Where they are having a problem is with the CocoaLumberjack dependency. |
|
For Android using the most recent version the compilation works fine, the only problem now it's iOS, I asked the team to provide all information of MABs so I can put here. I really need to solve that. My application stopped working and is totally dependent on your plugin. |
I will send this info to them. |
|
There is no comparison or correlation between what works for Android vs ios. They are as different as apples and oranges. |
|
Hi @alexandreafc, |
CocoaLumberjack@3.7.2 was released over a year ago. CocoaLumberjack is the most popular iOS logging library, used by tens-of-thousands of developers. It has existed for 12 years.. It is not some obscure, poorly maintained library. |
As you can see from CocoaLumberjack source-code, those symbols prefixed with |
|
Hi @Furkan68 thanks for your answer, how did you do? Did you fork the component or point direct to the tag like below: "plugin": I mean point direct I can't do a download properly. Thanks again. |
|
I doubt 3.7.0 will support iOS 15+ / Android 11+ You need to insist on OutSystems supporting |
|
Hi @alexandreafc, |
And this? There’s no possible way that 3.7.0 will work with Android 12. |
|
Hi @christocracy with this version was possible to compile in the OutSystems environment, but the component don't ask for permissions on Android 11 or 12, this version 3.7.0 should work on Android 11 at least, or shouldn't work? Thanks in advance. |
|
Android 11 didn’t exist when 3.7.0 was released. you need to pressure OutSystems to support the latest version of the plugin. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. You may also mark this issue as a "discussion" and I will leave this open. |
|
Hi Guys, I have downloaded the plugin code and added it as a resource to the Outsytems mobile plugin. With MABS 9.0 (Beta) and releas 4.9.2 of the plugin code, iOS is still not building with the same error; [2022-11-29T14:39:57.107Z] [VERBOSE] [Build] Undefined symbols for architecture arm64: With all due respect, but this is completely worthless. Both parties shift it a bit on each other and we are screwed. |
|
This issue is stale because it has been open for 30 days with no activity. |
|
This issue was closed because it has been inactive for 14 days since being marked as stale. |
Your Environment
#ready:Expected Behavior
We're trying to generate an iOS app through Outsystems for cordova-background-geolocation-lt plugin v-4.4.0
Actual Behavior
When generating the app it seems we are running into an issue with arm64
Context
When trying to generate the iOS app we're getting an error that the app can not be generated.
The sandbox application only uses actions needed for the plug-in. No other (extra) actions or screens are being used in this application.
Debug logs
Logs
The text was updated successfully, but these errors were encountered: