I am currently encountering some behaviour of which I am not sure this is expected.
In our app we want to send system profiling data along with the update request, so we did set our SUFeedURL to https://update.someserver.nl/update.php
In our update.php we filter out the profiling data and forward to appcast.xml.
We did test this and so far this is functioning correct.
Now, when the .app is zipped and generate_appcast is ran, the script generates a file called update.php instead of appcast.xml. The generated file's content is a correct appcast xml. If I rename the file to appcast.xml and upload the file to the correct location, all is fine.
Is this behaviour intended? Can I somehow set the preferred output appcast file name?
I am currently encountering some behaviour of which I am not sure this is expected.
In our app we want to send system profiling data along with the update request, so we did set our SUFeedURL to https://update.someserver.nl/update.php
In our update.php we filter out the profiling data and forward to appcast.xml.
We did test this and so far this is functioning correct.
Now, when the .app is zipped and generate_appcast is ran, the script generates a file called update.php instead of appcast.xml. The generated file's content is a correct appcast xml. If I rename the file to appcast.xml and upload the file to the correct location, all is fine.
Is this behaviour intended? Can I somehow set the preferred output appcast file name?