Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
I'm having the same problem and unfortunately there's no trace of the error (I can't find it on logs at least).
My scenario: I have an App Engine project for Java, with billing enabled, with running backends, with HRD (mirrored from an old Master/Slave project), some idle instances and no custom domain.
My scenario: I have an App Engine project for Java, with billing enabled, with running backends, with HRD (mirrored from an old Master/Slave project), some idle instances and no custom domain.
co...@gmail.com
I also have this error. Any idea?
nk...@gmail.com
I'm seeing the same problem. I believe this is the only way to use the Blobstore with Google Cloud Storage, correct? I'd be happy to create a different storage account but it doesn't seem possible to use the Blobstore/GS integration...
rf...@gmail.com
I too am having this problem with the application parrot-pairing, although the otherwise-identical app parrot-pairing-dev worked fine the first time.
ch...@gmail.com
It occurred to me that I have a separate Cloud Services project that I think was previously also named "parrot-pairing" but which I renamed to "parrot-pairing-db" when I discovered the names would clash. Could this renaming process have left some detritus around that poisoned the "parrot-pairing" name for cloud services projects?
[Deleted User] <[Deleted User]>
Thank you for the report. There are some errors which are not resolved by simply retrying. In the case of parrot-pairing I have found the bug which we will fix in a future release. When the fix rolls out, the retry should succeed.
The error information is not visible to application developers as it's an error in the implementation. However, given a particular app id we on the App Engine team can investigate further.
This is not the only way to use Google Cloud Storage and App Engine, although it is one of the ways we intend to accomplish our goal of simplifying the configuration of your application. There is more information on how to configure this here:https://developers.google.com/appengine/docs/python/googlestorage/
The error information is not visible to application developers as it's an error in the implementation. However, given a particular app id we on the App Engine team can investigate further.
This is not the only way to use Google Cloud Storage and App Engine, although it is one of the ways we intend to accomplish our goal of simplifying the configuration of your application. There is more information on how to configure this here:
ff...@gmail.com
Could you look into my app? The ID is whamcitylights
It would save me a lot of time to be able to use the Blobstore API integration with GS. I plan to slowly migrate to GS completely but I really can't afford to make the full transition right now. Thus enabling this integration would be huge benefit. Thanks
It would save me a lot of time to be able to use the Blobstore API integration with GS. I plan to slowly migrate to GS completely but I really can't afford to make the full transition right now. Thus enabling this integration would be huge benefit. Thanks
fe...@gmail.com
The issue with whamcitylights appears to be the same one--in fact I expect most cases are that same issue.
[Deleted User] <[Deleted User]>
Thanks! When do you expect the fix to roll out? Days? Weeks? Months?
rf...@gmail.com
We're getting this with two of our projects: bookedin-stage2 and bookedin-prod. We're finally upgrading to the latest version of mapreduce and would like to use the GCS file writer which appears to use the client library so I think we'll need this fixed for us.
rf...@gmail.com
Hello. I'm getting this error as well for app id colorfulsoftware-earthbeats. it is a java app with blobs.
ds...@gmail.com
I'm trying to activate Google Cloud Datastore, because Google Cloud SQL is not free. I'd like to use it as a database for my Google App Engine Application, with App Engine PHP. Basically PHP/SQL -> PHP/Datastore. I don't even know if what I'm doing is how Google Cloud Datastore supposed to work, but it'd be cool to see my nuts and bolts do something! Many Thanks to the developers for even having option available.
nk...@gmail.com
Add my app grooves-me to the list of those having this problem. I upgraded to paid for the app click upgrade under the cloud integration and then several attempts at retry. I am willing to help dev if they need anything from me.
he...@gmail.com
[Comment deleted]
he...@gmail.com
dc...@gmail.com
We are also experiencing this error. If there is a manual fix, please apply it to the following applications: ethosedge and ethosedge-sandbox. Thanks!
[Deleted User] <[Deleted User]>
Fixed as of 1.8.3
[Deleted User] <[Deleted User]>
Already fixed this problem?
We still face this issue.
We still face this issue.
Description
When I rotate the screen and select another tab in fragment app crashes.
Steps to reproduce:
- Create an AppCompatActivity that contains a fragment
- Fragment contains ViewPager + Tabs
- Each Fragment calls setRetainInstanceState(true)
- Assign a FragmentStatePagerAdapter to the ViewPager
- Run the app and rotate the screen, then switch tab
Tested on:
Nexus 6P
Android 6.0.1
Stack trace:
java.lang.NullPointerException: Attempt to invoke virtual method 'android.os.Handler android.support.v4.app.FragmentHostCallback.getHandler()' on a null object reference
at android.support.v4.app.FragmentManagerImpl.execSingleAction(FragmentManager.java:1623)
at android.support.v4.app.BackStackRecord.commitNowAllowingStateLoss(BackStackRecord.java:637)
at android.support.v4.app.FragmentStatePagerAdapter.finishUpdate(FragmentStatePagerAdapter.java:166)
at android.support.v4.view.ViewPager.populate(ViewPager.java:1235)
at android.support.v4.view.ViewPager.populate(ViewPager.java:1083)
at android.support.v4.view.ViewPager$3.run(ViewPager.java:272)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:858)
at android.view.Choreographer.doCallbacks(Choreographer.java:670)
at android.view.Choreographer.doFrame(Choreographer.java:603)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:844)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5417)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)