Thank you for the workaround!

I can see the appeal of staying inside the app, and would usually prefer it myself too, but cases like this do challenge the usefulness of that model.

FWIW, I’ve not come across posts from other sites exhibiting this yet, but then again I’m not following many WP blogs, and I suspect the issue could be prevalent there, as my settings for the ActivityPub plugin are pretty much at defaults.

I’m using the ActivityPub plugin to enable following posts from my WordPress blog. The posts federate as excerpts with a URL pointing to the full post on my site.

Tapping on that URL in the Android app only causes it to reload the post (excerpt) inside the app, instead of opening the URL in either webview or a browser as I’d expect it to.

The (official) IOS app does open the URL a browser, as does Firefox on the desktop, which is why I suspect the Android app being at fault here.

I don’t know of a way to link my blog here it so that it opens in the app (which is a bit ironic), but here’s a deck link to the federated posts on mastodon.social. My personal Mastodon account is on mastodon.social.

Both my Android phone and Android tablet are affected, both are on Mastodon version 2.2.1. The phone is running Android 10 (with Samsung’s One UI 2.0), the tablet is on Android 11 (One UI 3.1).

Below is a screen recording from the Android phone exhibiting the issue: the first tap of the URL opens the federated note in single view, and subsequent taps then just reload that same view.

I just tested uploading from the Nextcloud app, and it is similarly affected: no conflict dialog is shown and the existing file gets overwritten.

Steps to reproduce

1. Have a PDF file with the name ”ä.pdf” (sic) in your Nextcloud.
2. Have a different PDF file with the same name on your IOS device (Files app).
3. Choose to share the file from your IOS device to Nextcloud.
4. Select the folder where ”ä.pdf” already exists.
5. Upload.

Expected behaviour

Get a dialog to choose how to deal with the filename conflict.

Actual behaviour

No dialog. The the existing file is silently overwritten by the newly shared file.

Logs

Nothing in server logs, but here’s the app log (at the default level).

Reasoning or why should it be changed/implemented?

The issue leads to data loss. I discovered this when I realized that saving bills from my banking app by sharing them to my Nextcloud had been doing this for who knows how long. (My electricity bills have the service provider name, ”Oulun Energia Sähköverkko Oy” in their filename.)

Environment data

iOS version: 17.0.3

Nextcloud iOS app version: ”Nextcloud Liquid for iOS 4.9.1.0”

Server operating system:

Web server: Apache 2.4.41

Database: MySQL/MariaDB 10.3.38

PHP version: 8.2

Nextcloud version: 27.1.3.2

Miscellaneous

• This is not reproducible on Android (with my server), which is why I’m pretty sure the fault lies with the IOS app.
• Also not reproducible on IOS with filenames with ASCII-only names (FWICT); this general case was apparently fixed when first reported as Upload via Share Menu Silently Overwrites Existing Files #1737.

Summary

As of this writing, push proxy v5.25.0 was released 5 days ago, but the published assets on Github only include the source code.

Steps to reproduce

As per documentation,

wget https://github.com/mattermost/mattermost-push-proxy/releases/download/v5.25.0/mattermost-push-proxy.tar.gz

Expected behavior

Receive mattermost-push-proxy.tar.gz

Observed behavior (that appears unintentional)

404 Not Found

I have the same issue. I’m doing this in a Linux container (Ubuntu 20.04 inside Ubuntu 20.04), but like matthaios-easy-bi, I’m using npm run build:android to build (as per documentation). This has worked up until 2.0, but with 2.1 it always fails due to non-existent org.webrtc. Manually running npm install prior to npm run build:android makes no difference, nor does node node_modules/react-native-webrtc/tools/downloadWebRTC.js (although it does seemingly download the package successfully).

Here’s excerpts from the build output.

25.0.3 (as indicated by output from `occ –version` above).

The exit code issue is still there:

# sudo -u www-data /usr/bin/php /var/www/nextcloud/occ --version
Nextcloud 25.0.3
# sudo -u www-data /usr/bin/php /var/www/nextcloud/occ files:scan -- nonexistantuser
Unknown user 1 nonexistantuser
+---------+-------+--------------+
| Folders | Files | Elapsed time |
+---------+-------+--------------+
| 0       | 0     | 00:00:00     |
+---------+-------+--------------+
# echo $?
0

Hi @hmhealey,

Yes, it’s mainly about expectation. For an actual use case, I noticed this when mentioning an IRC channel name, which became a long, distracting and useless hashtag link, exacerbated by agglutination and multi-word hyphenation typical in Finnish, (e.g. #channelname-irc-kanavalla). I tried to make it less distracting by editing in a preceding backslash, only to discover that it didn’t work here.

Summary

There is no way to escape a word-starting hash character (#) in plaintext.

Steps to reproduce

In MM 7.3.0, post this, verbatim: \#anything

Expected behavior

#anything

Observed behavior (that appears unintentional)

#anything

Possible fixes

Workaround: instead of ”\#anything”, post this: &#​35;anything

Using backticks (`\#anything`) also works, but obviously the word then gets formatted as code and not plaintext.

Other notes

This is mainly an issue of inconsistency and surprise: backslash works to escape most other special formatting, so I’d expect it to work here too.