-
Notifications
You must be signed in to change notification settings - Fork 34
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
"Undefined symbols for architecture armv7" during device testing.. #5
Comments
have a look here: #2 |
the quick answer: remember to do this: https://github.com/viezel/NappUI#how-to-use |
Ah yes. That works. Btw, I had a the same issue with a module I wrote for a vertical ScrollableView class which overrides several methods, etc. Your symbol pre-loader technique fixed it as well. So this is one for the books.. this symbol pre-loader technique is needed if you write any module that needs to override delegate instance methods. For example:
Thanks for sharing your brain. |
Quick note about the preload technique. There's a slightly easier way to define the symbols without requiring users to
This will instantiate the symbols without requiring users to embed commonJS or JS object references.
The key here is Titanium statically analyzes the JS files to determine which symbols are needed before the JS interpreter is invoked. So all you need to do is reference the appropriate Ti.UI class, which marks it for inclusion during the compile process. I tested for device builds using both techniques. Thoughts? |
Hi Terry. Please do a PR if you don't mind. Again, great people are using this, and you have have any additional extended API, please submit them. |
Works great for simulator tests, but I'm having an issue with device testing. Seems the class files are undefined, which throws an error during app build. Can you test on your end?
Env:
The text was updated successfully, but these errors were encountered: