IOS crash when file URI contains spaces

[MarioUnlam]

Hi. There seems to be a problem with file URIs containing spaces, on iOS. If there's any space in the URI, either in a subdirectory or the filename, when I try to play it, the app crashes without any JS errors. I found out what whas happening thanks to a bug report from a different library, "react-native-track-player", so it seems to be an issue with the OS. The post mentions something about encoding the URI, but it didn't work for me. If I use encodeURI, the plugin simply fails to play the audio, so I guess it needs to be fixed on the native side. More info here:

https://github.com/doublesymmetry/react-native-track-player/issues/167 https://github.com/doublesymmetry/react-native-track-player/pull/950

Version of react-native-audio-recorder-player

3.6.4

Version of React Native

0.70.6

Platforms you faced the error (IOS or Android or both?)

iOS

Expected behavior

Play audio file normally, regardless of path

Actual behavior

App crashes without error

Steps to reproduce the behabior

1. Save an audio file in a folder containing spaces. For example: RNFS.DocumentDirectoryPath + '/My files/" + filename; Also happens if the filename has spaces.
2. Try to play the audio file using audioRecorderPlayer.startPlayer()

[fichtner]

To be frank, what automatic rules are you not able to disable?

Cheers, Franco

[c33s]

everything with ipv6 and i would like to have a rule which allows https access to the webgui from the wan but even if i create a rule for it is getting blocked by the default deny rule, which is strange because it is a "last match" rule and as far as i understand a "first match" rule which was defined by the user should be higher in priority shouldn't it?

[OPNsense-bot]

Thank you for creating an issue. Since the ticket doesn't seem to be using one of our templates, we're marking this issue as low priority until further notice.

For more information about the policies for this repository, please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.

The easiest option to gain traction is to close this ticket and open a new one using one of our templates.

[fichtner]

So you want to remove those rules that allow you to use DHCPv6 client on WAN... which effectively disables your IPv6 unless you add all the rules manually? The safest option is to disable IPv6 on WAN in this case?

[c33s]

@fichtner i want to disable ipv6 rules because my provider doesn't support ipv6 and i also don't use ipv6 in my lan. so all the predefined ipv6 rules only pollute my interface for nothing. it is not about allowing dhcpv6 on wan.

for the WAN i want to create a rule which allow access to the webgui (it is just for a lab setup) but as i wrote above, even if i create a rule which allows webgui access over the lan interface , access gets blocked by the default rules.

[bugoff]

I have the same issue as @c33s.

My opnsense boxes have their http / ssh interface open on wan for certain static ip's, and this isn't possible anymore. Is there an option to disable this behaviour as i use this on all my remote firewalls? This was possible on older versions.

[AdSchellevis]

@bugoff rules haven't changed recently, you can use the "Automatically generated rules" button on the interface to see which automatic rules apply on an interface (and usually how to disable them as well).

[bugoff]

@AdSchellevis it has been a while since i installed a new device, so i haven't noticed it before. The sshlockout rules don't have any info on them, and i can't find a way to disable them. If i read them correctly they reject traffic on the wan interface on port 22 and 443.

I added 2 new rules to enable ssh / https traffic to the firewall on port 22 and 443, but they aren't allowed.

[AdSchellevis]

ssh lockout means X faulty logins dropping your connection, that can't be an issue, but if it is, you can inspect the alias mentioned in the rule.

[bugoff]

@AdSchellevis Then i'm not really sure what i'm doing wrong here.

I'm currently testing this in my office, so it's a private range. I tested it with a floating firewall rule and a firewall rule on wan, the most basic rule i can think of.

The rule doesn't match and it always loads the default block rule. On the wan interface i disabled "block private networks and block bogon networks" (just in case)

[AdSchellevis]

best make sure to disable reply-to in the rule or in the advanced settings to prevent packets being send to the gateway address. I'm very sure you can allow access, our forum (https://forum.opnsense.org) might be a better place to discuss setup scenario's.

[bugoff]

For anyone having the same problem, this fixed it for me: https://forum.opnsense.org/index.php?topic=27983.msg141843#msg141843

[OPNsense-bot]

This issue has been automatically timed-out (after 180 days of inactivity).

For more information about the policies for this repository, please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.

If someone wants to step up and work on this issue, just let us know, so we can reopen the issue and assign an owner to it.

[wgzsh]

I'm encountering the same problem. It's quite inconvenient and poor user experience to restrict users from modifying these autogenerated rules.

I often resort to using pfctl -d frequently just to access the web UI. In my setup, Opnsense acts as a virtual firewall managing VMs within Proxmox. There's another firewall upstream, making the additional WAN rules a hassle.

[fichtner]

Can you be specific on what rules can’t be turned off?

[wgzsh]

Can you be specific on what rules can’t be turned off?

Any of the auto generated wan rules. More specifically the implicit deny all rule at the top of the list.

[mrfreezer]

having the same issue and spent ~10 hours on this so far. using the newest (24.7_9)