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.
Created attachment 17227 [details]
Video-recording of bug's behavior
See attached video:
It takes few seconds to render actual notification UI for the first time (after deploy to phone). Second notification renders fairly fast.
With Swift - there's no difference between first and second notification.
Is there any way to speed-up first load?
Please include your full build logs, crash reports (if any),
test case (to reproduce) and all version informations.
The easiest way to get exact version information is to use the
"Xamarin Studio" menu, "About Xamarin Studio" item, "Show Details"
button and copy/paste the version informations (you can use the
"Copy Information" button).
Xamarin Studio: 6.1 (5365) - see full installation info below / iPhone 6s (Beta 5);
I've also uploaded my test app into the DropBox:
Will free to check it out.
=== Xamarin Studio Community ===
Version 6.1 (build 5365)
Installation UUID: fb0e4a2c-12e9-4806-bfb9-5183f291bd0e
Mono 4.6.0 (mono-4.6.0-branch/23c6a4d) (64-bit)
GTK+ 2.24.23 (Raleigh theme)
Package version: 406000165
=== NuGet ===
=== Xamarin.Profiler ===
=== Apple Developer Tools ===
Xcode 8.0 (11228.2)
=== Xamarin.iOS ===
Version: 184.108.40.206 (Xamarin Studio Community)
Build date: 2016-08-23 14:45:42-0400
=== Xamarin.Android ===
=== Xamarin Android Player ===
=== Xamarin.Mac ===
=== Build Information ===
Release ID: 601005365
Git revision: 4fb2e8b3f2042f3be28b370d01f1c8057e993e51
Build date: 2016-08-23 08:54:41-04
Xamarin addins: 60c0f9d8f0eb210499e1f8c6daf4972c10f4663f
Build lane: monodevelop-lion-cycle8
=== Operating System ===
Mac OS X 10.11.6
Darwin Konstantins-MacBook-Pro.local 15.6.0 Darwin Kernel Version 15.6.0
Thu Jun 23 18:25:34 PDT 2016
When you run debug builds, the app is optimized to provide a great debugging experience which results on greater load times to memory (first run), subsequent ones are from code already in memory which is why it shows up faster. In the other hand release builds are very optimized and your app only contains what you actually use and load times are reduced significantly.
The other thing that you must have in mind is that extensions are resource limited by the operative system so they do not have the same resources available as a main app in foreground.
The good news are that if you run your app in release mode you should get great load speeds as shown in the following video.