mrdude wrote:RishavG wrote:Update on latest test version- I think i found the reason for crashes. Its vpn, for the first time i used vpn and the app immediately crashed and then i stopped vpn service it crashed again and after that couple of crashes i experienced 5 sec audio ad for the first time. @mrdude
OK cheers, it's difficult trying to fix this as I don't have any devices I can't login with - so trying to find the problem is just 'guessing', I'll need to leave it for now. I'll install bluestacks and see if I can get the login issue with that. I'll maybe have a look at the weekend when I get some time.
Crashing is caused because the app tries to download an ad as soon as Spotify starts and tries to put the ad in a queue and then starts a timer (but can't so the app crashes), I just removed 2 patched files to see what was causing the login issues - so now I know roughly what's wrong, so now I am closer to fixing.
After almost a day testing the "mod-v2", I had no problem, the app didn't crash and no ads appeared to me at the time I was using it, not even at the beginning. I always do clean installs and don't use VPN or Ads-blocks on that device.
I am testing the "mod-v3" and so far I was able to login without problems, the app doesn't crash and works normally so far on Android 4.4.2.
Previous days I was testing in BlueStacks 4 the first original version of the post that gave us some login errors, which uses Android 7 Nougat, the app always login correctly and worked well, in several of the device profiles that the app gives you a choice, such as: Google Pixel 2XL, Samsung Galaxy S10, OnePlus 5, Samsung Galaxy S8 Plus, etc.
But I noticed something curious changing the profiles between the different devices and using the spotify mod, and that is, for example: using the "Samsung Galaxy S8 Plus" profile, the app let me login normally without problems with my account that I use always usually. But trying a new account (created by not being able to log into my old physical device) the app said the error of wrong combination in email and password, when it was set correctly. This didn't happen if I used the "Google Pixel 2XL" profile, which allowed me to login perfectly both with my usual account and with the new account created.