To be honest though I had a tough week and will likely not do the testing till Monday. I also had a thought that it might be trying to go to a portal row that no longer exists? I will look closer to see if this could be what is happening. I did look though the log but did not see anything that looked like the pause idea for testing. I did find that there is a log for the iPad but I also saw they recommend not posting it public so I felt it was best not to post it. But while that will be interesting why would be crash at all if I run line 142 got to portal row? I have a few ideas for example my last tests were with a remote connection from FileMaker go and I will test that again and report back. But I can for sure replicate it crashing with the go to portal run on the iPad and it dose not crash when I comment it out. I am confident that I did get it to work by just moving the go to portal inside the if statement but as I am not able to replicate it I am having doubts that I can get that one to work again. I updated the original post last night with the comment out the go to portal row on line 142. This new mobile function allows developers to tap directly into the iOS device sensor information, including battery, location, speed, acceleration, air pressure, step counts, and more. I might have posted all this a little too soon as I guess I am still finding things. 0:00 / 13:28 In this video, we’re going to focus on the new FileMaker Go 17 Get Sensor function.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |