Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] APK install failure due to & in filename #69

Closed
penguinpages opened this issue May 5, 2023 · 5 comments
Closed

[BUG] APK install failure due to & in filename #69

penguinpages opened this issue May 5, 2023 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@penguinpages
Copy link

penguinpages commented May 5, 2023

Describe the bug

Attempting to download and install IFTTT software to work on some home automation.
Platform: Windows 11
I have four other Android Apps with IOT devices controlling fine so this is app specific.

Figured I would make a posting to see if this helps. The output is a bit lighton debug / logs / enabling higher log level

Source for APK
https://m.apkpure.com/ifttt-automation-workflow/com.ifttt.ifttt/download?utm_content=1008

Error

Unable to install the application. Please check ...blah blah..

[Error Info]
Performing streamed install
operable program or batch file.

Questions:

  1. within WSA-Sideloader -> can we run this via Powershell and set / increase logging from build and container?
  2. Has anyone else tried IFTTT and can provide feedback on there experience

I perused the "developer options" such as Select Debug App but .. no Debug App set and no means to set.

Steps to reproduce

  1. Launch WSA Sideloader
  2. Select IFTTT - automation & workflow_4.38.3_Apkpure.apk
  3. Install
  4. Get error
  5. reach for coffee

Expected behavior

App loads.. move on to next yak in line to shave.

Download source

Microsoft Store

WSA version

2303.40000.5.0

WSA Sideloader version

Version 10.0.22000.556 (Windows 11)

Windows build number

22624.1690

Additional context

No response

@penguinpages penguinpages added the bug Something isn't working label May 5, 2023
@infinitepower18
Copy link
Owner

Hi, just tried it and it seems like the file name is causing this error... I'll look further into this but for now can you rename the file to IFTTT.apk and then installing it?

@infinitepower18 infinitepower18 changed the title [BUG] [BUG] APK install failure due to filename May 5, 2023
@infinitepower18 infinitepower18 changed the title [BUG] APK install failure due to filename [BUG] APK install failure due to & in filename May 5, 2023
@infinitepower18
Copy link
Owner

Figured it out, it is due to & being present in the file name. I have found a fix for this issue and will release an update once I fix some bugs related to the partially running mode in WSA. I'm having exams this month so it may take a while.

@infinitepower18 infinitepower18 self-assigned this May 5, 2023
@penguinpages
Copy link
Author

The rename of file fixed this and worked fine. Thanks for response. Help with "how to debug" ex: what you did go get to that event error, would help. And good luck on your exams...

@infinitepower18
Copy link
Owner

WSA Sideloader uses ADB under the hood, the error info contains the output displayed by ADB which should be enough to investigate further. You can use ADB directly if you know what you are doing, the program is located in %LOCALAPPDATA%\Packages\46954GamenologyMedia.WSASideloader-APKInstaller_cjpp7y4c11e3w\LocalState\platform-tools or you can download ADB from the Android Developers website.

The operable program or batch file message was not by ADB but a standard windows cmd message, and when I encountered the same issue with the IFTTT app, it was clear it was something to do with the file name. This is because & is a special character used by cmd, along with some others:

https://en.wikipedia.org/wiki/Escape_character#Windows_Command_Prompt

As mentioned in the above link, prefixing the character with ^ will treat it like a normal character.

I've implemented the fix to handle such characters and will release an update this week hopefully.

@infinitepower18
Copy link
Owner

This issue has been solved in version 1.3.13 which is now available on the Microsoft Store. Thanks a lot for your support and patience. Do let me know any bugs you encounter in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants