-
Notifications
You must be signed in to change notification settings - Fork 1
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
Going back to a tab when it is showing a nested navigation stack causes an auto layout exception #19
Comments
I know, i knew your'd see it. |
It seems like there is a problem with the constraints that belongs to the UIWebview. At the moment I don't know why the error shows up the second time and not the first time when clicking on "My Profile", but we can look at the problem tomorrow. |
The same problem appears when viewing a question a second time. Steps to reproduce
|
That’s in the OPFQuestionHeaderView. A possible fix could be to disable automatic translation of auto resizing masks with On May 1, 2013, at 16:50, Marcus Johansson [email protected] wrote:
|
This issue isn’t resolved as far as I know? Still occurs in master for me (exact same steps to reproduce as previously). |
Well, on my computer no crash or error message was produced so that's why I thought it had been resolved :/ |
One way to solve this issue, as it seems to be caused by |
Right now I feel that we shouldn't change so much in the app since we will present it on thursday. The app is still working when the crash occurs and as long as we don't show them the console when we run the app we should be fine :) |
The app
crasheshalts at a debug exception the second time the “My Profile” tab is shown.Steps to reproduce
The crash
The crash occurs in the
-[AKTabBarView setContentView:]
method on line 47 due to some contradicting auto layout constraints in the OPFUserProfileViewController.Possible fixes
AKTabBarController
which is incompatible with auto layout and in such case fixAKTabBarController
./cc @tdeekens
The text was updated successfully, but these errors were encountered: