How to fix Android profile issues in Multilogin 6
Running into trouble with mobile profiles? You might face one of these two problems:
- Dimensions not showing (Windows): mobile profile dimensions aren’t displayed because of compatibility issues with custom device settings
- Android profile crashes (macOS/Windows): mobile profiles might crash or show a gray screen due to similar compatibility problems
There might be other small indicators of issues with Android profiles. Don’t worry, though – there’s an easy fix for most of them!
The simple solution
Add the following line to the app.properties
file in your .multiloginapp.com
folder:
multiloginapp.mobile.use_custom_device=false
Here's how:
app.properties
Windows
- Close Multilogin
- Go the
C:\Users\%username%\.multiloginapp.com
directory - Open the
app.properties
file with any text editor (for example, Notepad) - Make the necessary changes and save the file
- Launch Multilogin again and the changes will apply
Alternatively, you can go to "My account" in the Multilogin app and click "Open logs directory", then close Multilogin. In the window that will open, go one folder up. Afterwards, proceed from step 3.
macOS
- Close Multilogin
- Open your user directory in Finder
- Press
Cmd + Shift + .
(period) to show hidden files - Go to the folder
.multiloginapp.com
- Open the
app.properties
file with any text editor (for example, Notepad) - Make the necessary changes and save the file
- Launch Multilogin again and the changes will apply
Linux
- Close Multilogin
- Go the
/home/%username%/.multiloginapp.com
directory - Open the
app.properties
file with any text editor (for example, Notepad) - Make the necessary changes and save the file
- Launch Multilogin again and the changes will apply
Alternatively, you can go to "My account" in the Multilogin app and click "Open logs directory", then close Multilogin. In the window that will open, go one folder up. Afterwards, proceed from step 3.
Quick heads-up: after applying this fix, the OS might show as Android 6 instead of Android 10. This is a known issue, but it won’t affect functionality.