iOS Custom Keyboard Default code run takes over 40 MB in memory causing app crash
up vote
1
down vote
favorite
I’m making a custom keyboard extension in Swift 4.2 with Xcode10.
I'm new to create an extension in Xcode 10.
I created a single View application as a Containing App and added a target custom Keyboard extension.
And then as a trial, did run the default code WITHOUT any modification on iPhone 7 Simulator.
But this Xcode templated default code (which renders only the "next keyboard" UIButton) failed to run.
Error log says
App Crash
And after the first run failure, I did try the same run once more.
This time, it seems to be run normally in Simulator except memory usage.
The default code run memory exceeds over 40 MB. (WITHOUT ANY MODIFICATION both in the Containing app and keyboard extension ViewController!!)
Default Code iPhone 7 Simulator Run on iMessageApp
Could anyone have an opinion why memory usage in the default code run is so large?
swift memory crash keyboard
asked Nov 19 at 5:05
b kim
63
add a comment |
up vote
1
down vote
favorite
I’m making a custom keyboard extension in Swift 4.2 with Xcode10.
I'm new to create an extension in Xcode 10.
I created a single View application as a Containing App and added a target custom Keyboard extension.
And then as a trial, did run the default code WITHOUT any modification on iPhone 7 Simulator.
But this Xcode templated default code (which renders only the "next keyboard" UIButton) failed to run.
Error log says
App Crash
And after the first run failure, I did try the same run once more.
This time, it seems to be run normally in Simulator except memory usage.
The default code run memory exceeds over 40 MB. (WITHOUT ANY MODIFICATION both in the Containing app and keyboard extension ViewController!!)
Default Code iPhone 7 Simulator Run on iMessageApp
Could anyone have an opinion why memory usage in the default code run is so large?
swift memory crash keyboard
asked Nov 19 at 5:05
b kim
63
I think I found a reason why the first problem (app crash) occurs. It may be due to "Vacant" containing app. This link tells me that Apple doesn't allow containing app to be a skeleton app. The containing app must have at least one functionality, e.g., a TextView on the main screen in its storyboard.
– b kim
Nov 21 at 3:41
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I’m making a custom keyboard extension in Swift 4.2 with Xcode10.
I'm new to create an extension in Xcode 10.
I created a single View application as a Containing App and added a target custom Keyboard extension.
And then as a trial, did run the default code WITHOUT any modification on iPhone 7 Simulator.
But this Xcode templated default code (which renders only the "next keyboard" UIButton) failed to run.
Error log says
App Crash
And after the first run failure, I did try the same run once more.
This time, it seems to be run normally in Simulator except memory usage.
The default code run memory exceeds over 40 MB. (WITHOUT ANY MODIFICATION both in the Containing app and keyboard extension ViewController!!)
Default Code iPhone 7 Simulator Run on iMessageApp
Could anyone have an opinion why memory usage in the default code run is so large?
swift memory crash keyboard
asked Nov 19 at 5:05
b kim
63
I’m making a custom keyboard extension in Swift 4.2 with Xcode10.
I'm new to create an extension in Xcode 10.
I created a single View application as a Containing App and added a target custom Keyboard extension.
And then as a trial, did run the default code WITHOUT any modification on iPhone 7 Simulator.
But this Xcode templated default code (which renders only the "next keyboard" UIButton) failed to run.
Error log says
App Crash
And after the first run failure, I did try the same run once more.
This time, it seems to be run normally in Simulator except memory usage.
The default code run memory exceeds over 40 MB. (WITHOUT ANY MODIFICATION both in the Containing app and keyboard extension ViewController!!)
Default Code iPhone 7 Simulator Run on iMessageApp
Could anyone have an opinion why memory usage in the default code run is so large?
swift memory crash keyboard
swift memory crash keyboard
asked Nov 19 at 5:05
b kim
63
asked Nov 19 at 5:05
b kim
63
edited Nov 20 at 8:05
asked Nov 19 at 5:05
b kim
63
asked Nov 19 at 5:05
b kim
63
asked Nov 19 at 5:05
b kim
63
63
I think I found a reason why the first problem (app crash) occurs. It may be due to "Vacant" containing app. This link tells me that Apple doesn't allow containing app to be a skeleton app. The containing app must have at least one functionality, e.g., a TextView on the main screen in its storyboard.
– b kim
Nov 21 at 3:41
add a comment |
I think I found a reason why the first problem (app crash) occurs. It may be due to "Vacant" containing app. This link tells me that Apple doesn't allow containing app to be a skeleton app. The containing app must have at least one functionality, e.g., a TextView on the main screen in its storyboard.
– b kim
Nov 21 at 3:41
I think I found a reason why the first problem (app crash) occurs. It may be due to "Vacant" containing app. This link tells me that Apple doesn't allow containing app to be a skeleton app. The containing app must have at least one functionality, e.g., a TextView on the main screen in its storyboard.
– b kim
Nov 21 at 3:41
I think I found a reason why the first problem (app crash) occurs. It may be due to "Vacant" containing app. This link tells me that Apple doesn't allow containing app to be a skeleton app. The containing app must have at least one functionality, e.g., a TextView on the main screen in its storyboard.
– b kim
Nov 21 at 3:41
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53368611%2fios-custom-keyboard-default-code-run-takes-over-40-mb-in-memory-causing-app-cras%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I think I found a reason why the first problem (app crash) occurs. It may be due to "Vacant" containing app. This link tells me that Apple doesn't allow containing app to be a skeleton app. The containing app must have at least one functionality, e.g., a TextView on the main screen in its storyboard.
– b kim
Nov 21 at 3:41