So I just updated to 2.0.3 on my iPad (iOS 7.1.2), and now the game no longer works. It starts, crashes, and puts me back at the iOS desktop. I've been waiting months for a separate fix related to the Restore Purchases option not working, and you guys take it a step further and prevent me from playing at all...
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
I'm sorry you've had this problem. I've had no problem like this on any of my iOS devices, and we haven't yet had any other such reports either.
But of course it's likely the update was not tested on iOS 7; mine are all on 9.2 of course. Is yours an original iPad? Or what model of device exactly?
But of course it's likely the update was not tested on iOS 7; mine are all on 9.2 of course. Is yours an original iPad? Or what model of device exactly?
I believe it is an iPad 2, I can confirm this once I get home from work.
However I don't see how this should matter. The game ran fine under iOS 7.1.2 before the 2.0.3 update, and now it doesn't. There were no update details specifying a particular iOS version requirement, and even if there was one, the game should not have been allowed to install and break my existing working version at that point. Where is the Quality Assurance team in all of this? Are Paradox iOS applications not tested for backwards compatibility?
However I don't see how this should matter. The game ran fine under iOS 7.1.2 before the 2.0.3 update, and now it doesn't. There were no update details specifying a particular iOS version requirement, and even if there was one, the game should not have been allowed to install and break my existing working version at that point. Where is the Quality Assurance team in all of this? Are Paradox iOS applications not tested for backwards compatibility?
I'm not saying it should have had this problem, that it's OK that it did. Just that it's unsurprising, to me anyway.
Once you have the details settled let me know and I'll pass them back to the developers.
Of course they are, but iOS 7 is very old, and again it wouldn't entirely surprise me if it wasn't in the test suite. I don't know for certain either way.
Once you have the details settled let me know and I'll pass them back to the developers.
i have an old iphone 4 with iOS 7.1.2 and i can confirm the game no longer works.it just crash. i can see the game menu double-tapping the home button, but if i try to redume it' just show the paradox logo and minimaze it again. worked fine till the 2.0.3 update. i completed the first dlc just 2 days ago and was looking forward to the new expansion 
The page on app store still mention ios7+ as minimum requirement, just i case you need to update it
The page on app store still mention ios7+ as minimum requirement, just i case you need to update it
My exact model is iPad2 - MC770LL/A. Though the iPad itself may be a bit on the older side, I wouldn't necessarily call iOS 7.1.2 old, as it was released in July of 2014, making it just a year and half old. I specifically haven't upgraded to 8 or 9 due to all the issues I've seen my friends have with those newer versions on their iPads. And I don't personally prescribe to Apple's push it forward mentality; that I need to buy their latest device just because they released one. So it'll be a while until I upgrade to a newer device.
Well, it's old in Apple years
Apple themselves no longer support it. According to this support matrixhttp://iossupportmatrix.com/
The iPad 2 can go to iOS 9, so you don't need to update your hardware, just iOS; that's all I can suggest for you. We can't develop to an unsupported OS.
FYI my iPad 2 did, and now my iPad Air 2 does, run with iOS 9 perfectly fine. I'm not sure what bugs you are referring to there!
i have an old iphone 4 with iOS 7.1.2 and i can confirm the game no longer works.it just crash. i can see the game menu double-tapping the home button, but if i try to redume it' just show the paradox logo and minimaze it again. worked fine till the 2.0.3 update. i completed the first dlc just 2 days ago and was looking forward to the new expansion
The page on app store still mention ios7+ as minimum requirement, just i case you need to update it
If you have an iPhone 4s, you can update to iOS 9 and the game will work again.
Whereas if you have an iPhone 4, then iOS 7 is the last version available from Apple. If that is the case we don't have much to suggest, I'm afraid; close all background apps ( such as iTunes and Spotify , anything really) before starting the game. Or just restart the device entirely to clear memory, then try the game.
Apple have stopped supporting iOS 7 themselves, so there's nothing more we can do I'm afraid.
I hope that helps!
PS: I will look at getting the App store requirements updated - thanks for pointing that out!
I just spoke with a general Apple support representative who assured me iOS 7.1.2 is still supported on all compatible devices. I also spoke with a Apple developer representative inquiring about legacy OS support who told me there should be no reason why inquiries against iOS 7.1.2 would not be supported. So where exactly are you getting your information, because I'm getting mine straight from the horse's mouth.
It seems like Paradox just doesn't care about their customers, who without, they wouldn't have a business.
The facts are:
1. KoPP2 v1.0 through v1.09 works on iOS 7.12.
2. KoPP2 v2.03 is listed on the app store as supporting iOS 7.0 or later.
3. KoPP2 v2.03 does not work under iOS 7.1.2.
4. As of 01/18/2016 there are 12 reviews of this game on the app store (8 of which are 1 star negative reviews about this same crash/bug)
5. As of 01/18/2016 this thread has 3 separate people complaining about issue.
So why is it again that Paradox won't investigate and or fix this issue? Because it's easier top go update their app store page to say it only supports iOS 8.0 and higher than it is to actually fix the game so people who paid for it can actually use it. Thanks Paradox, you've go some great customer support going on there.
It seems like Paradox just doesn't care about their customers, who without, they wouldn't have a business.
The facts are:
1. KoPP2 v1.0 through v1.09 works on iOS 7.12.
2. KoPP2 v2.03 is listed on the app store as supporting iOS 7.0 or later.
3. KoPP2 v2.03 does not work under iOS 7.1.2.
4. As of 01/18/2016 there are 12 reviews of this game on the app store (8 of which are 1 star negative reviews about this same crash/bug)
5. As of 01/18/2016 this thread has 3 separate people complaining about issue.
So why is it again that Paradox won't investigate and or fix this issue? Because it's easier top go update their app store page to say it only supports iOS 8.0 and higher than it is to actually fix the game so people who paid for it can actually use it. Thanks Paradox, you've go some great customer support going on there.
Last edited:
.png){kind=avatar}
Hello there! Hope you don't mind if I join in.
The behavior both you (Xorcist) and Arcadio describe, sounds like an automatic app shutdown due to insufficient memory.
The smooth thing to say is that we're looking into ways of reducing the memory footprint (and we are). To be very frank with you, we can't yet say how far we'll succeed in that.
Question 1: OK, but is there a way of reducing memory consumption manually?
Two things that some of you may have already done:
Question 2: So what about the OS support thing?
It's definitely true that Apple continue supporting iOS7 for the end-user. You can still download the update, you'll be answered if you have customer support questions, etc.
At the same time, Apple has re-built (and significantly improved) a whole lot of their developer-facing systems over the last two years. For example, they've completely changed the standard way of testing in-development apps (Google "TestFlight" if you want the details). As a result, a lot of the infrastructure we use to build and test apps pre-supposes iOS8 and younger. This is one of the reasons verifying this isn't very easy for us right now.
When Andrew asked me about this issue before, I answered with my 'developer goggles' on. That's my bad. Sorry for the misunderstanding.
The behavior both you (Xorcist) and Arcadio describe, sounds like an automatic app shutdown due to insufficient memory.
(In case anyone's interested: That's standard behavior on both iOS and Android, where they'll start closing apps to regain memory. Usually background apps, but in extremis, also those that're currently running. Ever had Safari / Chrome just close on you in the middle of a browsing session? 8/10, that's what it was.)
The smooth thing to say is that we're looking into ways of reducing the memory footprint (and we are). To be very frank with you, we can't yet say how far we'll succeed in that.
(In case you're still interested: The game itself had no real change to its start-up memory footprint between Fo+1F and HbD. A current hypothesis (that may be wildly inaccurate) is that there is an increase due to one of the middlewares (like Unity). This patch updated several of them to their first post-iOS9 versions. Sometimes, what's optimized for the younger OS, runs worse on the older. This isn't very easy to verify, though.)
tl;dr: We're trying to make this game work on as many of your devices as possible, but if I promised you specifics, I might be a liar.
Question 1: OK, but is there a way of reducing memory consumption manually?
Two things that some of you may have already done:
- Close all background apps.
- Some (itunes, Spotify, messengers, etc.) reserve memory and have high system priority, so that the new app may close before them.
- Restart your device.
- It's not unusual for a device that has been in use for years to gather one or two apps with memory leaks (program parts that slowly keep grabbing memory due to a bug). Switching it on and off again is the nuclear option for temporarily plugging those leaks.
Question 2: So what about the OS support thing?
It's definitely true that Apple continue supporting iOS7 for the end-user. You can still download the update, you'll be answered if you have customer support questions, etc.
At the same time, Apple has re-built (and significantly improved) a whole lot of their developer-facing systems over the last two years. For example, they've completely changed the standard way of testing in-development apps (Google "TestFlight" if you want the details). As a result, a lot of the infrastructure we use to build and test apps pre-supposes iOS8 and younger. This is one of the reasons verifying this isn't very easy for us right now.
When Andrew asked me about this issue before, I answered with my 'developer goggles' on. That's my bad. Sorry for the misunderstanding.
Okay so now we're getting somewhere. Thank you for your detailed outline of potential reasons for this issue. It's nice to know the devs are aware of this issue and making an effort to analyze it. I'm a developer myself, and it pains me when customer issues are seemingly brushed aside in a "just re-install" or "just upgrade your OS" fashion. I deal with some large corporations building enterprise level web applications that still need to support IE8 (believe it or not). And we do our best to ensure everything works for those clients until they are ready to upgrade (which often takes upwards of a year sometimes, to migrate a entire company, as change management is a long process).
But back to the matter at hand. I have attempted a full shutdown, restart, and then just running KoPP2. However nothing was different, the issue persisted. A friend suggested I try to install an app to monitor and log the RAM usage on my iPad (noting that the iPad2's and iPhone 4's only had 512MB of RAM). I will attempt this when I get home from work today and post my results here.
I do hope with more information and more time, the code can be optimized enough to get it running again.
But back to the matter at hand. I have attempted a full shutdown, restart, and then just running KoPP2. However nothing was different, the issue persisted. A friend suggested I try to install an app to monitor and log the RAM usage on my iPad (noting that the iPad2's and iPhone 4's only had 512MB of RAM). I will attempt this when I get home from work today and post my results here.
I do hope with more information and more time, the code can be optimized enough to get it running again.
Okay, so it looks like KoPP2 v2.03 is currently using about 300MB of RAM on a newer iPad4, my iPad2 only has about 150MB of RAM free, and 50MB inactive (not sure it that counts toward anything). I tried to free up more of the RAM, but wasn't having much luck. Either way, it looks like the RAM could definitely be an issue. Is there any way to get v1.09 back on my iPad?
Apple will only host one version of a game at a time, unfortunately. We can't do a roll-back like we can on Steam.
Can I ask what app you are using to monitor memory use? Just so we can use it too and get consistent readings.
Can I ask what app you are using to monitor memory use? Just so we can use it too and get consistent readings.
I used System Status by Techet. It doesn't do per-app memory usage, but I was able to view the free memory before starting KoPP2 and then after it started, and then just took the difference. This was on an iPad4 running iOS9. Obviously on my iPad2 the game would crash out, so I couldn't get a reading there, but I was able to see I had limited free RAM. Would there be somewhere the system logs "out of memory" errors like this, so I could get you more info?