-
Notifications
You must be signed in to change notification settings - Fork 56
RateLimit is not Bitcode compatible #18
Comments
Those symbols appear to be related to the |
Go for it |
I don't know how to fix this. I disabled the build setting and get the same error. I can't find any other build settings and I don't see anything suspicious in the build log. @soffes can you think of any reason the compiler would emit coverage-related symbols for this framework? |
No idea :( You could try just deleting the project and making a new one maybe. It's such a simple framework. Annoying that it's causing so much trouble. |
Ok. I'll take a look at it again later. Thanks! |
@calebd take a look at the scheme. Specifically: https://github.com/soffes/RateLimit/blob/master/RateLimit.xcodeproj/xcshareddata/xcschemes/RateLimit-iOS.xcscheme#L30 |
Good call @mattbischoff! |
😄 |
I don't think that's it. I have coverage turned on in other frameworks and those do not have this problem. I found another coverage-related build setting that was turned on that is off by default in new Xcode projects. |
Both of the build settings referenced in the above commits were added in 3f34224. |
Done |
@soffes, I remember that an issue was opened for this a while back, SlatherOrg/slather#73. It sounds like we should definitely come up with a solution |
Cool. Wanted to make sure you knew about it @marklarr 😄 |
This one is hard to explain. If I upload a build that both contains RateLimit and has Bitcode enabled I get this:
Thanks to @mattbischoff, I found the following message in this developer forum thread:
And indeed there it was:
I'm now trying to figure out exactly what these symbols are and why they are allegedly referenced from RateLimit. I will post back here when I know more.
The text was updated successfully, but these errors were encountered: