Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
When a user is using the trial version of Xamarin.iOS, a "trial" splash screen is used to show that the app is part of a trial but when a user purchases the full version and does not have a launch screen set, the "trial" splash screen still shows, confusing the user thinking that their app is still in trial mode.
The splash screen is added by the addin
They can do a clean rebuild to work around this issue.
*** This bug has been marked as a duplicate of bug 2844 ***
The problem is that when you do a build, we only copy new files into the app bundle. We don't clobber the app bundle and then re-populate it with all files.
In other words, if you remove files from your project and then build, they will still be in the app bundle until you do "Build -> Clean" or "Build -> Rebuild".
(Rebuild just calls Clean and then Build)
I just committed a patch to work around this by creating a monotouch_trial file in the obj/ directory. When the user then builds the first time after upgrading out of Trial, that file is checked - if it exists, the build process deletes all of the launch images in the app bundle before continuing, thus forcing all launch images to get re-installed if the user has any defined (if not, no launch images are installed).
Great, that sounds like a nice solution to work around this issue, thanks Jeff!