View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011656 | MMA | General | public | 2013-12-23 04:32 | 2013-12-27 06:29 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | block | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.0.4 | ||||
| Target Version | 1.0.4 | Fixed in Version | 1.0.4 | ||
| Summary | 0011656: MediaMonkey Pro Upgrades fail with MediaMonkey Beta | ||||
| Description | If the user is running the beta, and the 15 day timer expires, then a dialog appears indicating that the app has expired, and giving the user the option of: a) check for / installing a new beta b) getting MediaMonkey Pro If the user clicks the 'Get Pro' button, then the user is sent to the Play store to purchase/install MMA Pro, however, this process consistently fails to upgrade the app: --> the upgrade silently fails--the MMA Beta relaunches with the warning dialog displaying. --> moreover, once this failure occurs, MMA sometimes continues to run indefinitely and must be force-terminated Note: I wonder also whether running MMA Pro would fail if MMA is running (in my testing I verified that MMA had in fact terminated before running MMA Pro), and if that would be a problem, then clicking the button to purchase pro should probably also terminate MMA, at least in the case of an expired beta. Tested on Nexus 5 running Kitkat, using MMA Beta build 209, and MMA Pro 1.0.1 release. Both were installed via sideloading. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 210 | ||||
|
|
Further testing shows that MMA Pro does unlock the regular build of MMA, however, the unlock dialog only occurs when Pro functionality is first accessed (as described at #11643). Maybe that's the root of this bug--that the unlock doesn't occur as soon as the app is run, but rather only when a Pro function is accessed? |
|
|
Fixed in build 210. Pro App package renamed to "com.ventismedia.android.mediamonkeypro", all links updated. |
|
|
Is com.ventismedia.android.mediamonkeypro correct? I see that in the store it's currently: com.ventismedia.android.mediamonkey.professional Unless--is that link taken from the package? |
|
|
Fixed in build 1.0.2 Pro 1.0.2 version is needed. Pro project package renamed to "com.ventismedia.android.mediamonkeypro". Signatures from all aps must be same.. Marek's 210 build looks different.. I let know to him. |
|
|
This works as expected with Martin's build 211. Leaving unverified to check with final build from Marek. |
|
|
Verified with Marek's build 213 / 1.0.3 |
