7.0.3: android-cloud-api error

[Huster-at-github]

After upgrade from 7.0.2 to 7.0.3 there is an Android App Error:

FolderSync can't connect anymore. Other Apps as "ES File Explorer" or the two Owncloud-Apps are still working.

access.log:
79.232.202.xxx - - [12/Nov/2014:08:12:22 +0100] "PROPFIND /owncloud/remote.php/webdav/ HTTP/1.1" 400 8731 "-" "android-cloud-api - Android 4.4.2"

Android 4.4.4 also reported this bug.

See also same bug in OC 8.0:
https://forum.owncloud.org/viewtopic.php?f=29&t=23983

[LukasReschke]

Can you please report a complete issue report using the issue template as stated at https://github.com/owncloud/core/blob/master/CONTRIBUTING.md? - Thanks.

[Do-D]

Hi,
just fyi, since the upgrade to 7.0.3 it does not work with the android app "synchronize ultimate" either.
It's a free XDA App if someone likes to test: http://forum.xda-developers.com/showthread.php?t=2412188

It did work with 7.0.2.
Owncloud Sync client, iOS App and Owncloud Android App are still working.
No owncloud or Nginx error log.
Nginx access log:

10.31.31.254 - {USERNAME} [12/Nov/2014:15:27:41 +0100] "PROPFIND /remote.php/webdav/ HTTP/1.1" 400 2901 "-" "Sardine/0.0"

[volker-fr]

I debugged this future and came to the point where it fails in lib/base.php init

if (!OC::$CLI
   // overwritehost is always trusted
  && OC_Request::getOverwriteHost() === null
  && !OC_Request::isTrustedDomain($host)
) {

The error here is that the the isTrustedDomain() function resolves it as "false" and therefore fails.

Comparing the $host variable between a working client and a not working client indicated that the not working system provided the port and is therefore not trusted.

Passes: my.owncloud.hostname
Fails: my.owncloud.hostname:443

[volker-fr]

My workaround fix is adding the host name with :443 into the config.php. The first entry (labeled 0) is the default one, the one labeled "1" is the new one.

  'trusted_domains' =>
  array (
    0 => 'my.owncloud.hostname',
    1 => 'my.owncloud.hostname:443',
  ),

[Do-D]

This worked for me too, Thank You!

[Huster-at-github]

Sorry for the late reply and YES, your workaround is working! - Thanks!

[StraToN]

I had problems synchronizing CalDAV entries of my server on Android since the update. The workaround #12123 (comment) (volker-fr) did the trick.

[skavoovie]

Disregard previous report that the fix didn't work for me in Thunderbird. I forgot about the Thunderbird Lightning URL work-around ( http://forum.owncloud.org/viewtopic.php?f=3&t=2894 ) when setting up a test server.

Thanks for the work-around!

[juliadin]

Thanks, the workaround did work for me, too. Since this problem was introduced with my installation being upgraded to 7.0.3 and the 7.0.3 - will there be a fix for that, so that the workaround is not necessary anymore?

[sloniupl]

ownCloud 7.0.3 (stable) - great workaround, now foldersync android app works correctly with my owncloud (webdav) :)

[LukasReschke]

This will be fixed with 7.0.4. Sorry for the hassle. - In the meanwhile I'd like to ask anyone experiencing this problem to adjust the trusted_domain setting as pointed out above.

[ghost]

Adding :433 to the trusted domain in config.php solved this issue for me too. Thanks

[lysathor]

Modification of trusted_domain in config.php solved this issue for me too. Thanks

[alexander-yakushev]

Not contributing much, but worked for me too! Thanks a lot.

[rbrueckner93]

workaround fixes issue. thanks!

[ceremcem]

thanks for the workaround!

[salfter]

So that's why FolderSync was giving me fits earlier. I replaced it with the ownCloud app at F-Droid, but then I saw that calendar entries weren't updating. The :443 workaround mentioned abovr got calendar sync working again.

OTOH, it would now appear that Keepass2Android can no longer sync to an ownCloud WebDAV share. When it tries to access the file, it briefly says something like "could not open from remote" in a popup that goes away after a couple of seconds. The aforementioned workaround makes no difference. I can load that program's database through (for instance) ES File Explorer, but that'll be a read-only copy.

[timaba]

Thanks for the workaround!

[owenashurst]

Hmm. I've added my domain with ":443" on the end like stated above, but instead of getting "Bad Request" I'm now getting, in FolderSync, "Attempt to read from field 'java.util.Listbbi.a' on a null object reference".

If I choose OwnCloud as the account type, then I get "Method Not Allowed".

Any ideas?

[dnorwood]

This workound works great, was beating my head against the wall earlier.

[comamondo]

found this after same problem -> SOLVED, thanks!!

[ghost]

Cool! This worked for me too! Thanks!

[mtudury]

Thanks for the 'trusted_domains' workaround.

i've found that the domain name is case sensitive too !
my.domain.name does not allow users with settings defined : my.Domain.Name (mobile devices virtual keyboards...)

Regards

[volker-fr]

@mtudury: I would create a new ticket for the case sensitive issue. This ticket is already closed and it is unclear if someone in charge will read your comment.

[salfter]

Following up:

OTOH, it would now appear that Keepass2Android can no longer sync to an ownCloud WebDAV share. When it tries to access the file, it briefly says something like "could not open from remote" in a popup that goes away after a couple of seconds. The aforementioned workaround makes no difference. I can load that program's database through (for instance) ES File Explorer, but that'll be a read-only copy.

At some point (first noticed it maybe a month ago), Keepass2Android started working again. I don't know if it was an update in Keepass2Android or in ownCloud (or both), but it's nice to have my passwords synced again. Other apps depending on WebDAV might also work once again.