After tapping on models that end with .stl app crashes
Project Information
Repository: https://github.com/andresoviedo/android-3D-model-viewer
- Project Name: 3D Model Viewer
Expected behavior
All model are expected to be clickable, easy on rotating and perform well.
Actual Behavior
After loading models that end with .stl and tapping on it the app crashes.
How to reproduce
- Download and install the application here
- Lunch the application
- click on Models
- Select any model that ends with .stl
- After loading
- Tap on the model
And the app crashes
Also by using the load model
- Lunch the app
- Click on load model
- Select from your file models that end with .stl
- tap on the model and the app crashes
Application version: 2.0.1
Operating system: Android v7.0
Hello @olamatto, After several attempt on my devices, i was unable to replicate the behavior, the feature seems to work perfectly as expected, if that tends to be happening on your device then provide the logcat, maybe that will be of help to the PO....
Thank you for your contribution
Need help? Write a ticket on https://support.utopian.io.
Chat with us on Discord.
[utopian-moderator]
Can't reproduce
![11.gif](https://steemitimages.com/DQmccc67Sg2xNLKom2HSBHwYwp1aPW19oFC72sPH7METKhU/11.gif)
But, other model I tried loading failed to do so. I suspect these issues are already known to the PO, as can be seen with this bug report:
https://github.com/andresoviedo/android-3D-model-viewer/issues/34
The issue reported in the link you provided is totally different, even how to reproduce it is diferent, the user there is talking about demo.
It's a bug report by one of the utopian community manager, which details how the app crashes when he tries to play a demo. It's not the same, but definitely not totally different.
Please make use of a mobile phone not pc, using the same operating system, and see how it works.
No dude, that's not how testing works. Bug should be able to being reproduced on any device that is supported by the software version. If the error is relevant only for your device (which BTW you didn't specify), then it's not really a bug with the code, more a bug with your hardware, so to speak.