Bug 35820 - [iOS] Today Extension Memory Warnings
Summary: [iOS] Today Extension Memory Warnings
Status: RESOLVED ANSWERED
Alias: None
Product: iOS
Classification: Xamarin
Component: Samples ()
Version: master
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: (C7)
Assignee: Oleg Demchenko
URL:
Depends on:
Blocks:
 
Reported: 2015-11-12 16:20 UTC by Matthew Regul
Modified: 2016-02-17 19:41 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED ANSWERED

Description Matthew Regul 2015-11-12 16:20:16 UTC
Working on with the Today extension for iOS you'll receive memory warnings no matter how small the data loaded into extension is, even with single object.  This can happen with a brand new Today extension project, including the sample app from the website.

It seems to only happen on physical devices, including the iPhone 6 running 9.1, and also 8.2, and never in simulation.

Sample App - https://developer.xamarin.com/samples/monotouch/ios8/ExtensionsDemo/

**See Private Comments for more details**
Comment 10 Oleg Demchenko 2016-02-17 19:41:32 UTC
With the fix of bug 38817 Today Extensions should work fine now.

Resolving this bug as answered.