fun(...) crashes in iOS for versions of Language-Ext later than 3.1.24
See original GitHub issueI have observed, that every version later than 3.1.24 causes a crash on iOS, when creating a function using fun(...)
.
I’ve created a simple project to illustrate this issue here: https://github.com/1iveowl/Language-Ext-Issue-Recreate.
Run the iOS project on a real device and press the button number 2, and you will get a crash from the line var testFunc = fun((int x) => Task.Delay(TimeSpan.FromSeconds(x)));
.
In the project I use Language-Ext version 3.3.20. If I change the project to use Language-Ext version 3.1.24 then the crash will no longer occur.
Note: I’ve only seen the issue on a real iOS device. If I run the project in the simulator I do not see a crash.
Might be related to #632
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
MTOUCH : error MT3001: Could not AOT the assembly #537
I've encountered a pretty strange issue when building on certain machines where the build will fail: MTOUCH : error MT3001: Could not AOT ......
Read more >App Crashes in iOS 16. Unable to find crash reason
App was successfully running on iOS 15, build and pushed to appstore via Xcode 13.2. But after iOS 16 beta release, app was...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Don’t do this “one by one”. Cut your search space in half each time just like binary search.
Start with some set of
static
values such that the program crashes. Comment out half of them. Test. If the program crashes, then repeat with the set ofstatic
values still commented in. If the program did not crash, then repeat with the set ofstatic
values that were just commented out.My guess is that you are merely searching in
Prelude
for some static value that extends fromRecord<>
, which means that this issue is a special case of #632.My mistake. The first paragraph have now been updated. I hope this clears the confusion?