SOLVED!
For reference, the binary that was in the "bitcodeless" branch on GitHub had indeed the bitcode removed, but it had left the bitcode marker. This was causing Transporter to think the executable still had bitcode. We removed the bitcode marker as well (using the bitcode_strip command line tool that is included in the Xcode bundle).
I suggest you to crete a new branch...
@info-6
We need to know if there is a problem with the suggested branch or not, in order to avoid hours of frustration.
Replacing the code, changed the Apple store answer from "contains bitcode" to "contains incomplete bitcode".
Still, we are not able to update our App using Xcode 14.
Please respond..
Thanks.
Hello.
I tried and, in Transporter verification I got the following response:
Asset validation failed (90668)
Invalid Bundle Executable. The executable file 'Referi.app/Frameworks/flic2lib.framework/flic2lib' contains incomplete bitcode. To compile binaries with complete bitcode, open Xcode and choose Archive in the Product menu. (ID: 80e8e166-de4e-4d0b-99d5-7fb578683079)
We have a iOS App that uses the Flic2 SDK.
Yesterday, on our last update of the app, we received this error message from Apple.
Is it something wrong with the SDK or does it regard only our SDK implementation?
Urgent, please...
Apple message:
We identified one or more issues with a recent delivery for your app, "Referi" 1.1.7 (2). Please correct the following issues, then upload again.
ITMS-90482: Invalid Executable - The executable 'Referi.app/Frameworks/flic2lib.framework/flic2lib' contains bitcode.
Forgot to say:
I installed the Flic App on the TvBox.
Beside the fact that it runs sideway (like if the TV set was a phone) when I try to add aFlic button, it ask for location permission (correctely):
"You location services are turned off.Android requires location services to be turned on to scan for Bluetooth devices."
"Please tunr on Location services and try again"
When you press to confirm it opens the OS setting for Location (correct) where, being a TvBox, there is only the choice "Use Wi-Fi to estimate location" or "off".
Chosing the first, does not solves the problem. The OS reports still that "no apps have requested location recently"
Our App, using the Flic library, is working fine on Android 10 TvBox.
Due to supply shortage we had to move to a Android 11 TvBox (A95XW2) and we are not able to pair the buttons.
It almost get to the end but then the folvogin message appears:
I noticed some recent changes on the Flic Android lib on GitHub (2 months ago). Is our problem due to the fact that we implemented the Flic library for Android a couple of years ago and not updated it or is there something else?
Thanks
Is this problem involving also the developer library of Flic2?
We have a customer who has the S10 with Android 11, and he is not able to pair the Flic with our App.
Same problem here.
The Flic2 buttons are much less reliable then the Flic1.
Something to do with the hardware switch bouncing?
Some buttons works some other don't repsonde correctly to the 3 form of click.
I agree to this.
Would be nice a Flic wereable version, like a Fit wrist band (3 buttons?)
On a iOS implementation, scanning for a Flic2 Btn, I sometime receive this error:
Operation couldn't be completed. (com.shortcutlabs.flic2lib.buttonscanner error7.)
Supposing that this is not introduced by my developer, that implemented the SDK, what is error code 7?
There should be somewhere an easy to find "numbered" list of Flic error, so that we can take care of problems.
Is there?
Thanks
I am receiving this error, trying to pair a Flic2 button on iOS 13.5.1 using the sdk:
"The operation couldn't be completed. (com.shortcutlabs.flic2lib.buttonscanner error 1)"
Is there any way to find out what's wrong?
As of two days ago I was using, on a iOS 9.3 iPad, the flic1 buttons and the Flic App 2.2.16. Everything worked fine.
Yesterday there was no trace of my Flic1 button anymore on the Flic App and I am not able to pair the button anymore:
error code f8: "There was an error trying to connect to our servers. Please check your internet connection...".
While I think the metal clip developed for the Flic 2 buttons is not in my opinion a great improvement (it hides the led light, for example), we find it problematic to use it because of the adhesive back of the button, that it is also not removable.
Often, trying to clip the button to a shirt, the protection plastic gets peeled away.
Are you planning any improvement on this?
Is there a reason why the Flic2 framework ask on Android (not on iOS) to authorise position location?
Our developer, that is implementing the Flic2 library for our App, told us that in your API there is no way to detect, on opening the library, if the system bluetooth is on or off and, consequently, advise the User.
While we solved that on iOS, I would like to know if there is a way, in the Android API, to do this.
As you can image, having the bluetooth off without knowing it, the user may think that is the App that doesn’t work and we have no mean of how to advise him of this fact.
Thanks
I think that when on mobile an App (with the Flic library) goes to background, while background clicks are not enabled, there should be a way to disconnect buttons or close the library after a while, so that they save batteries level.
The typical user behaviour, once done, is to go to another App or close the cover of a tablet and forget about it. Rarely they quit an App.
That said, while i think there is a time-out on Android, I am not sure how to manage this on iOS.
Can someone please explain?
Thanks
Flic2Lib.
iOS: The callback on is not sent when I manually disconnect a Btn. Works fine when going out of range.
Android: works fine on both cases.
iOS 13.3.1 Android 5.0
On iOS, for some reason the flic objective-c library isn’t calling the delegate method when a button is disconnected. Anybody else had this problem?
As I mentioned before, I understand that it has been stated that the minimum iPAD to be used with the FlicApp is 4th generation (?).
I just want to remark that there are around a lot of iPAD with iOS 9.3, whose OS cannot be updated and could be put to a good use with the Flic buttons.
It works fine with Flic1 buttons but not with the new Flic2.
Is there a way to fix it?
The new Flic2 buttons apparently don't pair anymore with the Flic App 11.3 on OSX 10.14.6 (Mojave).
Is this me or there is a problem?
(Same for FLicApp 4 on iOS 9.3 of iPAD)