-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unit tests stuck #99
Comments
@raphaelguye - it includes too many code changes in new releases, it might not be a good idea to dig into the changelog.
|
Thank you for your answer. That's why I'm asking if there is something special in your changelog between these two releases? |
Hey @timliu55, i'm taking over this issue from raphael since hes away. Like he said we are whitnessing a problem while running the unit tets with our MAM application. Raphael has tried releases from 23.8.0 back to 22.5.0. The break happenes between versions 22.5. and 22.8. Regarding your other suggestions, debugging is not really effective since the application starts as expected but the testrunner never executes. |
@dzwick-bit , I just compared our code changes from 22.5 to 22.8, there are too many changes, but most of them are bug fixings, "iOS 16 compatibility" means some bugs appear on ios16 only We need to find what happened in your side, at least we need to find some error message, could you please try below:
|
We have some issues with the run of our unit tests when trying to upgrade from v22.5.0 to v22.8.0 or above.
When we integrate v22.5.0 to our project, everything is fine and all of our unit tests are executed with success.
When we integrate v22.8.0 (or above), some tests are just stuck and the process never ends.
Can you tell us a bit more about the changelog between 22.5.0 and 22.8.0?
It said "iOS 16 compatibility", but is there any breaking changes? Our app is targeting iOS 13.
The text was updated successfully, but these errors were encountered: