(11-14-2020, 07:45 PM)solid Wrote: Sending phyphox-file to myself by e-mail works well for my Android (send from PC where the file is edited, received by the smartphone with phyphox).
On iDevices, there is one intermediate step: the file needs to be shared to the app phyphox. Tapping just gives the source code.
(11-14-2020, 07:45 PM)solid Wrote: With Brest wishes
Over there I thought it was about opening the experiment? Your screenshot looks like gmail or is it something else? For me sharing works as well. I will have to check if I received a crash report with more details...
11-27-2020, 03:04 PM (This post was last modified: 11-27-2020, 03:06 PM by solid.)
I am very much sorry. Sending phyphox program via e-mail does work normally and I do not know what I did wrong before the lunch.
I am sending the file as an attachment from my personal computer using the university e-mail to my gmail read by my smartphone (Android) with phyphox installed. Then it is sufficient to click to the attachment and the new application can be saved to my phyphox collection.
I have verified the file version sent earlier creates this problem of phyphox crash while attempting to be added to the collection. So, I attach this file here. In the new version I only removed all parts mentioning the phyphox editor ...
It is the same file that we discussed for 'gausssmooth'.
This is a XML thing. It defines editor:* as a prefix, so the XML parser of phyphox know that it can ignore these. If it is not defined, phyphox does not know that this is a prefix and tries to interpret the attributes itself. Of course it should report the problem instead of crashing, but if you have editor:...-attributes, you need to define this.
Edit: It will no longer crash in the next version. However, the XML parser handles this problem a bit "unconventionally" (at least in my opinion) by generating an entirely different type of exception, which is why it caused a crash instead of being displayed in the first place. The resulting error message will be a bit cryptic, but since this is a rather unusual error, we can probably live with that.