I don't know what happened, but all of a sudden the builder is not recognizing the methods. I checked, they are listed in schema.graphql.
I do
amplify push
but it doesn't work.
I think it started happening after I ran modelgen build.
If I look at the model in
app\src\main\java\com\amplifyframework\datastore\generated\model
the methods are there.
Todo todo = Todo.builder().name(0).build();
Cannot resolve method name in 'NameStep'
I ended up deleting the files in app\src\main\java, and running modelGen again, a couple times, and it started working again. I am not sure what happened, but this seemed to make it work.
Related
I've been scouring the internet looking to see if anyone else is hitting this problem, maybe some one else here has seen this recently. I'm integrating Google Play services and using Firebase database with Google Play authentication in a Unity project.
screenshot of autocomplete list with missing class:
For some reason, I seem to have every component of Firebase.Auth except PlayGamesAuthProvider, which is needed to call the GetCredential function. I'm seeing this error:
error CS0234: The type or namespace name 'PlayGamesAuthProvider' does not exist in the namespace 'Firebase.Auth'. Are you missing an assembly reference?
I've reinstalled my Firebase package already and double checked everything for clashing plugins. I'm really hitting a wall here, just curious if anyone else has seen this problem and knows how to get around it. Thanks in advance!
If anyone stumbles across this with the same problem, I've got it working. First tried to reimport the latest Firebase.Auth package from Firebase and that didn't fix the problem. I actually tried doing it a second time, making sure that all files were being re-imported, and then also re-imported the latest GooglePlayGamesPlugin package. I'm not sure which fixed it, but there was clearly something breaking down in there, maybe more-so related to the GooglePlayGamesPlugin. I even disabled/renabled my Unity services. Bottom line, keep reinstalling your stuff and eventually it will work. If I notice anything more specific I'll follow up.
In my Laravel 5.3 application I am using several Eloquent model events (mostly creating). Up until a week ago they were working fine but suddenly as of today I notice that none of them seem to be firing anymore.
Debugging through the framework shows that they are indeed all added to the Dispatcher::listeners array, but I can't find the code that should step through and actually run them. Placing die() commands in the event callbacks do nothing, suggesting they are not acutally firing, and nothing I try seems to get them working.
Here is an example of one of them (this one is on a trait, but I am using a mix of traits and direct model):
public static function bootUuidModel() {
// On create, generate and assign a UUID
static::creating(function (Model $model) {
$model->setAttribute(self::getUuidFieldKey(), Uuid::uuid4()->toString());
});
}
Anyone have any ideas as to why these are suddenly not running? I am using them across various models for various purposes and none of them seem to be running. Has anyone else using the framework experienced these problems as of late?
Thanks in advance
--UPDATE--
Okay so after some more investigation I've found that the problem is that the User object is for some reason booting BEFORE Laravel's DatabaseServiceProvider is booted. DatabaseServiceProvider::boot() for some reason is where the event dispatcher is statically assigned to Model. So any booting in the User object is not registering the events with the dispatcher because the dispatcher doesn't exist yet. I am not booting the User object myself, does anyone know why Laravel would be doing this?
The problem is that when i try to update the service reference i get the following error.
The checkout was cancelled by the user.(0x80004004)
I can't seem to do anything that will solve it since if i do try to do something then i have problem with pending changes.
When you Update Service References, changes are made to files in ProjectDirectory/Service References/Your Service Namespace.
These files aren't shown in the solution explorer, but they should be in source control so other team members don't have to manually update references.
Try checking out these files and updating again.
We are getting intermittent problems on a production server that we cannot recreate.
There are two very strange things about the issue. Firstly it's a method not found error on the constructor (ctor) for an exception handling helper class and secondly we have custom errors switched on for remote users and this property is being ignored.
The detail of the error is:
Server Error in '/MyWebsite' Application.
Method not found: 'Void MyExceptionHelperClass..ctor (System.Exception)'.
...
Exception Details: System.MissingMethodException: Method not found: 'Void MyExceptionHelperClass..ctor (System.Exception)'.
...
The stack trace is pretty unhelpful.
My thoughts are that there may be an out-of-memory error or something like that that is killing the page. When the exception handling code kicks in it tries to create an exception object which fails for the same reason giving this error.
However this is wild speculation. We are waiting for the event logs to see whether anything is amiss with the server but in the meantime does anyone have any thoughts or suggestions?
UPDATE:
It has proven difficult to get information out of the team responsible for the production servers but I have managed to find out that as far as load balancing is concerned, this site is currently only running on one server (this can be made to switch over onto another if necessary). Given that this is an intermittent problem and there is only one server involved, then I find it difficult to believe that this could be an assembly issue. Surely if it was then the problem would occur every time?
If you see this error happening on a site that has custom errors turned on, then the error is happening in the custom error handling routine itself.
From the look of the .NET error message it appears that your routine is expecting a constructor that accepts an exception by reference - your comment above shows a constructor that accepts by value.
Check carefully that there isn't a stale version of an assembly in your system somewhere. These can lurk in the Temporary ASP.NET Files folder; you'll need to do an "iisreset /stop" before you can clear them out.
In that regard it's always a good idea to make sure that AssemblyInfo.cs is set up to automatically stamp version numbers in some way. We have our version numbers tied to our source code repository system and CI build box so we can tell exactly what was in what assembly really easily.
I would use elmah: http://code.google.com/p/elmah/ to hopefully give you a bit more insight into the issue. It is free and can be used on an existing site without any recompilation. Try it - and post back if the issue is still happening.
As others have also mentioned, I would suspect that your site is somehow using an out of date version of an assembly. Something you could try doing is a full Precompile of your site before deploying to your production server. This ensures that ASP .Net doesn't dynamically compile the site on the fly, and therefore should mean that it's using completely up to date code throughout.
Do you have a no parameter public constructor defined for MyExceptionHelperClass in your code? Or is the class meant to only have static methods, in which case it should be a static class.
public class MyExceptionHelperClass()
{
public MyExceptionHelperClass() { }
}
Unfortunately, this may be one of those cases where the error message is of little to no value. In my experience, this general class of exception may be the result of either a configuration issue or bad logic aroung threading/app domains. For example, I have seen similar issues upon attempting to load the same assembly into an app domain more than once.
You mention that this is difficult to reproduce. If it's only happening on one server in the production farm it's more likely to be a config issue (with that machine). If it's happening on more than one server than it could be either config or threading.
It might be worth spending some time looking at the larger code base around the areas mentioned above. The root cause may not be in this class. Good luck!
I think it's a Framework issue with keeping compiled versions consistency. It's common to see same sort of errors while updating site sources repeatedly. Just try something like
net stop iisadmin /y && del /q /f /s "%systemroot%\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\*.*" && iisreset
I encountered this exception today on a webforms page. I found a solution, but I'm not sure why it worked.
Nest the code behind in a 'Namespace [YourNamespace]' tag.
Add the namespace to the html Page tag's Inherits property in the aspx page 'Inherits="PathStart.YourNameSpace.ClassName"'.
Rebuild
Navigate to the page again and you should not encounter the exception.
After following the steps above I reverted the changes and did not re-encounter the exception.
I could use some help trying to track down an intermittent error that I've been having with our ASP.Net project for quite some time.
Intermittently when building the solution, the build will fail with the error "/: Build (web): Object reference not set to an instance of an object." The error has no associated file, line, column or project information. The weird thing about the error is that it will go away on successive rebuilds and doesn't seem to result in any run-time errors that we've come across once the build is successful. Sometimes the error will pop only once, sometimes 3-4 times, but eventually the build will finish successfully and then seems to build just fine each time after. I haven't been able to nail down a pattern as to why and when the error will happen, and since it always eventually builds it hasn't been a critical problem for us. Just an annoyance. But one that I want gone for obvious reasons.
I guess I should add that this is an application that was originally developed in ASP.net 1.1 and converted to 2.0 and I inherited it somewhere down the line after that, so I don't know when the problem originally surfaced. As far as everyone here is concerned, it's always been there.
Obviously I'm not expecting someone to pick out the cause of my problem as that would require them to look at our entire solution to pick out potential problems. Just hoping someone can give me a couple fresh ideas as to how to go about tracking down the actual source of the error in code. It has to be coming from somewhere, right? How would you go about finding out where?
I've seen this when you have a web control in a page where there is invalid HTML. If your codebehind is trying to do something with the control, it won't be able to find it and will give you Object Reference... error at compile time. In my experience, it doesn't create a runtime error, and the project will build if the file in question is closed at the time of build. HTH, Good Luck!
Run this command at the command line and see if you get some more detailed information
%WINDIR%\Microsoft.NET\Framework\v3.5\msbuild.exe YourSolution.sln /v:n
To follow up on this problem, we never did track down the origin of the error but it disappeared when we upgraded to Visual Studio 2008 and converted the project to a Web Application.
The first thing I'd try would be to increase the compiler verbosity. This can be set in the Visual Studio options - e.g. "Tools->Options->Projects and Solutions-Build and Run->MSBuild project build output verbosity" for VS2005. If you set it to diagnostic then it should tell you what it's doing at the time the exception is raised at the very least.
I had this problem for a long time and finally found a solution that work fine for me.
It doesn't make sense to me... but altering my web.config file with the following gets definitively rid of this intermittent build error :
<buildProviders>
<add extension=".rdlc" type="Microsoft.Reporting.RdlBuildProvider, Microsoft.ReportViewer.Common, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
<!-- add this line below -->
<remove extension=".rdlc"/>
</buildProviders>
Hope this help !
I had this at build time when my project contained custom datasources (my own objects returning collections) with compile errors (that is, my objects had errors).
You'll also get this error if you try and add a datasource and your project doesn't have any datasources in the project's root (e.g. if you've put all your datasource classes in a subfolder). The only solution I found was to create a datasource in the project's root.
Sorry not to be more precise, but there seems to be several things that can go wrong with datasources/objects at compile-time.
An "Object reference not set to an instance of an object" is clearly a run-time error, not a compile-time error. So what that says to me is that Visual Studio is choking on something, which may not necessarily be in your code, or which something in your code is only indirectly causing.
Next question I'd ask: Does this happen only in Visual Studio, or does the same thing show up when you build using MSBuild or CSC?
What's really odd is that it's a run-time error. You shouldn't see that at compile time. Do you have any pre- or post- build steps attached to the solution? Any unit tests you're including with your 'build' process?
Where does this error show up?
Check the Application Log of your Event Viewer - It should tell you where the exception is being thrown.
Just to clarify, is it the compiler itself that is choking? Are you doing anything weird with #define and #if directives in your code? Maybe something is being done out of order at some point... Just a thought...
See if there are any post-build events that could be failing. These can be found on each project's property page.
Try using Rebuild Solution instead of Build Solution. You may need to add Rebuild Solution from Tools > Customize. If your web app installs or registers any windows services, and those services are started, Rebuilding plows through those types of problems.